package telnet
reassign 237268 telnetd
thanks
The dominant cause for this behaviour lies within the server
built from the same source package. In fact two causes are
rather straightforward:
1. The server telnetd built from netkit-telnet is not able
to process variables transmitted as USERVAR, as is specified
in RFC 1572. A Solaris client would transmit $FOO, as in the
initial report, as a USERVAR to the server, whereas our client
built from netkit source, would denote it as VAR. This is an
acceptable protocol variation.
2. The direct cause of failure is the fact that the original source
for telnetd-0.17 maintains a short and hard-coded list of variable
names to accept into the environment. All other variables are dis-
carded! To be exact
TERM, DISPLAY, USER, LOGNAME, POSIXLY_CORRECT
are the only acceptable variables.
2'. The code for parsing ENVIRON in telnetd-0.17 is in fact adapted
to the legacy BSD convention OLD-ENVIRON, except that a macro has
been altered to run the same code only with NEW-ENVIRON, and other-
wise to decline any processing of OLD-ENVIRON. An effort to rework
said code portion to strictly follow the better protocol NEW-ENVIRON
is a prerequisite before the hard-coded list should be relaxed.
Best regards,
Mats Erik Andersson
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
