On Fri, 3 Sep 2021, Florian Weimer wrote: > We increasingly see a situation where the terminal has some UTF-8 locale > (usually en_US.UTF-8), but the remote end does not recognize that and > falls back to the POSIX locale, often quite noisily. The noise of the fallback is the only problem with that, though. I tend to have my locale settings in my ~/.mkshrc on either side, so I get sanitised locale environment parameters anyway. This is the easiest, and perhaps the most reliable, way to fix this (for interactive/shell sessions) but outside of the scope of ssh… 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
