Locale problems on Solaris

[Ben Lindstrom]

Maybe instead of loading up OpenSSH's do_setup_env with hundreds of
potentally unique user variables we should provide a sshd_config option
like 'ChildEnv' which would allow the admin decide what they would to
export.

Then provide Solaris, AIX, etc examples of 'commmonly used' ones
somewhere in contrib/ or in (cringes) sshd_config.

It seems a bit more reasonable then having 30+ different #if
_SOMEPLATFORM/#endif code in OpenSSH portable.

Granted it is semi-redundant since /etc/environment serves the same
thing.  Just ensuring people remember to update it when changes
occur.

- Ben

On Tue, 26 Feb 2002, Daniel Bergman wrote:

>
> I agree with Dan!
> Since init reads /etc/default/init and then, on most systems anyway,
> launches SSH from /etc/rc[23].d/S[00-99]opensshd, sshd parent process
> should have the "correct" locale setting. So copying those variables from
> the parent seems like the right approach.
>
> Coping LANG, NLSPATH and LC_* variables into /etc/environment might not be
> a bad idea for sysadmins anyway. /etc/profile or ~/.profile should source
> that file.
>
> Regards,
> Daniel
>
> > This may be a usable workaround, but it's the wrong solution.  Despite
> > appearances, /etc/default/init does NOT contain environment variables
> > (per se).  Aside from LANG and LC_*, it contains configuration for
> > /etc/init such as TZ and CMASK, which should not get folded into the
> > user environment.
> >
> > It would be preferable to copy LANG, NLSPATH, and all variables
> > beginning with "LC_" into /etc/environment or $HOME/.ssh/environment.
> >
> > If you want to fix it in sshd, you should do it by copying those
> > variables from the parent sshd process to the session, not be reading
> > /etc/default/init.
> >
> > --
> > Dan Astoorian               People shouldn't think that it's better to
>
>
>
> --
> Daniel Bergman
> Phone: 08 - 55066265
> Mobile: 070 - 289 30 39
> Fax: 08 - 59827056
> Email: d-b at home.se
>