[6165] in Kerberos
Re: Why TELNET sends arbitrary environment variables at all?
daemon@ATHENA.MIT.EDU (Peter da Silva)
Wed Nov 8 01:07:51 1995
To: kerberos@MIT.EDU
Date: 7 Nov 1995 21:07:11 GMT
From: peter@nmti.com (Peter da Silva)
In article <47nsh1$o7h@sungy.germany.sun.com>,
Casper H.S. Dik - Network Security Engineer <Casper.Dik@Holland.Sun.COM> wrote:
> peter@nmti.com (Peter da Silva) writes:
> >My question is, why did they set up Telnet so it passed arbitrary environment
> >variables at all? About the only ones I can think of worth passing are "TERM"
> >and "DISPLAY".
> That's precisely where the problem starts. You think only of TERM/DISPLAY.
> But what about:
> TZ
What does *my* TZ have to do with that of a system I'm telnetting
to, anywhere in the world?
> TERMCAP (descibing the complete terminal entry)
If your TERM is correct, then this can be regenerated. If it isn't,
you're hosed anyway... lots of systems don't use TERMCAP.
> LESSCHARSET
Generate from TERM.
> WINDOWID
Is this some NeWS thing?
> PRINTER (in local environment)
> LPDEST (as PRINTER)
Hmmm.... maybe.
> LC* (localisation)
> EXINIT
> LANG
These are pretty much static.
> there are probably many more that are pretty portable.
But how many are (a) portable, and (b) dynamically changing? TERM, DISPLAY,
maybe printer, and NeWS stuff. I'm gonna patch my telnet to ignore anything
that isn't in /etc/environment (maybe with default values...).
--
Peter da Silva (NIC: PJD2) `-_-' 1601 Industrial Boulevard
Bailey Network Management 'U` Sugar Land, TX 77487-5013
+1 713 274 5180 "Har du kramat din varg idag?" USA
Bailey pays for my technical expertise. My opinions probably scare them
