Re: locale problem

From: Daniel Rock (abuse_at_deadcafe.de)
Date: 05/27/05 

Date: Fri, 27 May 2005 17:18:31 +0000 (UTC)

Laurent Blume <laurent=//=pas_de_pub/news200505@elanor.org> wrote:
> Look at those tries:
[...]

Had the same problems. Seems to me like a bug in the locale negotiation.
I just set on the client host (which issues the ssh command) the environment
variable SSH_LANGS to an empty string. Now sshd initializes the LC_*
environment from /etc/default/init.

On the source machine I had set:

LC_MESSAGES=de
LC_NUMERIC=C
LC_*=de_DE.ISO_8859-1

LC_ALL and LANG were unset.

IMHO ssh and sshd should at most only set the LC_* variables which were
set at the source host, not LANG and even less LC_ALL - which overrides
any other locale settings anyway.
And it shouldn't set them to a *.UTF-8 locale, while all variables on
the source host suggest a ISO_8859-1 or POSIX locale.

This (mis)feature of Sun's ssh is quite annoying. 

-- 
Daniel

Relevant Pages

  • Re: [5.2.5] Supporting European locales?
    ... the PHP site doesn't work as planned: ... For those interested, here's what I found out, on a FreeBSD 6.3 host: ... dateonly uses the US locale, ...
    (comp.lang.php)
  • Re: UTF-8 on 8.0-CURRENT: Yes We Can!
    ... My Freebsd is only used as a server I access to by ssh. ... these options to the kernel and put my locale in utf8 it would work ok? ...
    (freebsd-current)
  • Re: some changes after upgrading Testing (locale ,gv)
    ... When I do ssh to my university, ... > couldn't set locale correctly ... > I should also mention that some packages are yet to be upgraded: ... > Building dependency tree... ...
    (Debian-User)