Comment 16 for bug 920749

(In reply to comment #13)
> Getting around this bug by using another variable is really not a good
> way. Many shells have different initialization paths (even for the same
> shell: login and not login shells).

Even no initialization at all (e.g. "ssh -t host command" with upstream bash on the remote host).

> Maybe there should be an option to set, so that the admin can choose
> whether pam should come first or not. I can code that.

Shouldn't there be a way to do both? e.g.
1. PAM sets defaults.
2. SendEnv/AcceptEnv variables are overridden by sshd.
3. PAM does locale-name conversions, if possible (because the local name conventions on the local and remote hosts are not the same).