Date: Thu, 29 Nov 2018 14:16:56 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 233624] SSH got closed when enterying non-ASCII characters Message-ID: <bug-233624-227-5lfCIAwU6z@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233624-227@https.bugs.freebsd.org/bugzilla/> References: <bug-233624-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233624 Yuri Pankov <yuripv@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jilles@FreeBSD.org --- Comment #5 from Yuri Pankov <yuripv@FreeBSD.org> --- Thanks, reproduced. The obvious "workaround" here is setting LANG and MM_CHARSET using ~/.login_conf (or /etc/login.conf, see 22.2.1 in https://www.freebsd.org/doc/handbook/using-localization.html). For the problem itself, I'm seeing the same on 12.0-RC2, but not on 13.0-CURRENT (as of 20181126); setting LANG in ~/.shrc shows the same probl= em.=20 I'm not sure whether this is a bug per se, or what has exactly "fixed" it in -CURRENT. To sum up, the problem is: - have /bin/sh as login shell - don't have any locale customizations, so that you have "C" everywhere in locale(1) output - try to input/paste multibyte character; BEL is echoed back; no output - do: LC_ALL=3Den_US.UTF-8; export LC_ALL (or put it in ~/.shrc) - try to input/paste multibyte character; connection is closed. May be Jilles could have some ideas on what has changed? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233624-227-5lfCIAwU6z>