Created attachment 2597 [details] proposed patch In our Red Hat bugzilla, we have such report, that this is not expected behaviour. For us it is obvious, that TERM variable is send and accepted regardless configuration, because it is part of protocol. This doesn't have to be obvious for some users so it should be mentioned in manual pages. I propose such simple sentence (see attached patch).
Committed a reworked patch. Thanks, it will be in the 6.9 release.
I didn't check what you wrote there (unfortunately). Few remarks for your upstream commits: https://anongit.mindrot.org/openssh.git/commit/?id=85b96ef41374f3ddc9139581f87da09b2cd9199e https://anongit.mindrot.org/openssh.git/commit/?id=43beea053db191cac47c2cd8d3dc1930158aff1a https://anongit.mindrot.org/openssh.git/commit/?id=c1d5bcf1aaf1209af02f79e48ba1cbc76a87b56f ssh_config is ok sshd_config: > environment variable is always sent whenever the client > requests a pseudo-terminal is requested as it is required by the protocol. * variable is not sent, but accepted * "requests a pseudo-terminal is requested" doesn't make sense * [...] client requests a pseudo-terminal [...] * or * [...] a pseudo-terminal is requested [...] * but please not both
fixed, thanks -requests a pseudo-terminal is requested as it is required by the protocol. +requests a pseudo-terminal as it is required by the protocol.
Reopening this, as the manpage in master still reads: "environment variable is always sent whenever the client" for the AcceptEnv directive, while it should read "... accpted ..." as it has been pointed out by Jakub before. Cheers, Chris.
Oh and one more: I would at least hope (though I haven't checked) that TERM is only accepted when sshd actually allows to create a PTY (can someone check whether this is the case?). Therefore it should read: "whenever a pseudoterminal is created as it is required by the protocol." because it may not be created even if requested by the client, namely if forbidden e.g. by PermitTTY.
Fixed s/sent/accepted/ Someone fixes the duplicated phase a while back.
closing resolved bugs as of 8.6p1 release