Re: Conflicting TERM env var with SetEnv feature.

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

 



On 17/11/18 12:32 am, Raphael Medaer wrote:
Actually if you use "-o" it's also overridden. Looking at sshd
logging, it seems that the env var is overridden because of session
mechanism (aka "not ordering of parameter source").
Thus is it a non-issue due to priority of configuration source ? Does
it mean that the priority is "env var" > "cmd line arguments" >
"configuration directive" ?

Tl;dr: you are right, and TERM is special.

Reading the source, I see that TERM is treated specially.  This is explicit in ssh_config(5), which says, "Note that the TERM environment variable is always sent whenever a pseudo-terminal is requested as it is required by the protocol."

Whether or not the configuration should be able to force a different TERM than the environment is a matter for debate. TERM is used far and wide, and needs to be consistent with the actual terminal hardware, so forcing its value in ssh's configuration file seems wrong.

Note, also, /etc/ssh/ssh_config is not *the* ssh configuration, merely the default.  Any user can replace it with a file of their own choosing.

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev




[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux