Why the limitation on Windows environnment introduced in OpenSSH 4.0?
Corinna Vinschen
vinschen at redhat.com
Sat Nov 13 20:46:05 EST 2010
On Nov 11 10:51, kevin gurney wrote:
> Here's the complete description of *Bug 915*
> <https://bugzilla.mindrot.org/show_bug.cgi?id=915> - [PATCH] Only
> copy basic Windows environment:
>
> So far, the whole environment is copied over to child processes
> started from sshd when running under Cygwin. The attached patch
> restricts this to the basic environment created for all processes.
>
> (https://bugzilla.mindrot.org/show_bug.cgi?id=915)
>
>
> Corinna Vinschen was the author of the bug report. Are you reading
> this list, Corinna?
At that time the patch was requested by Damien for security reasons,
AFAIR. Cygwin was the only platform which propagated the environment of
the privileged user running sshd to the process spawned for the user
just logging in.
[...time passes...]
I just found the related thread in the ML archive:
http://marc.info/?l=openssh-unix-dev&m=109232852213455&w=2
If you need more environment, it has to be created within your user
session, as on other systems(*).
Corinna
(*) For instance, fill ~/.ssh/environment. Or use ~/.ssh/rc to run a
script which fills the environment with values from the registry.
Or add a script to /etc/profile.d. There are a lot of methods
available, some of which have been discussed on the Cygwin ML
already. Check the archives.
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
More information about the openssh-unix-dev
mailing list