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! ****************************************************
On 2022-04-27 21:48:07, Thorsten Glaser wrote:> On Wed, 27 Apr 2022, Harald Dunkel wrote: > >> 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. >I would love to, but please see this: https://bugs.debian.org/965323 https://bugs.debian.org/952516 Anyway, the idea is to add an official statement like Ingo's "SendEnv LANG LC_*" is a terrible idea into the source files to take influence upon the package managers. Regards Harri
On 27.04.22 21:48, Thorsten Glaser wrote:> On Wed, 27 Apr 2022, Harald Dunkel wrote: >> 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.Sure, because "have server setting blindly trump clients'" is *so* much better than "have client setting forwarded blindly to the server". And here I thought that, after OpenVPN painstakingly retrofitting one into their data channel setup, "when you need an agreement, you need an explicit negotiation phase" would be a commonly accepted tenet now ... (As in, *let* the client send his settings, then have the shell's startup phase run a helper application that edits the env vars as necessary to achieve compatibility with the server's capabilities.) Regards, -- Jochen Bern Systemingenieur Binect GmbH -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3449 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20220428/bd64e3a0/attachment-0001.p7s>