On Wed, 27 Apr 2022, Harald Dunkel wrote: > Anyway, the problem here is that MacOS sets a locale "UTF-8" in > LC_CTYPE instead of "en_US.UTF-8", which produces problems even > though UTF-8 is available on all involved systems. That’s the name of the UTF-8 locale on recent OSX, yeah. Caused quite a few “WTF” looks. It loosely corresponds to “C.UTF-8” ever since the Debian (e)glibc maintainers accepted my proposal for it (MirBSD also basically only has the UTF-8 and ASCII locales, so it was natural to propose a C.UTF-8 for GNU stuff) around 2013 or so. Some systems have “en_US.UTF-8”, some “en_US.utf8” (HP-sUX!), and again some only have, say, “de_DE.UTF-8” but not the latter two (hence the introduction of C.UTF-8). > Maybe you should consider to add some guidelines about how to handle > locales into a README within the openssh source package, or in > ssh_config(5), sshd_config(5), etc.? Pretty easy: handle them on the server, period. There’s no way to do it otherwise. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg **************************************************** /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption! **************************************************** _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
