Hello,
first of all, I found out, that if I enter a sane login name (does
not need to exist) and press enter twice, then I can safely enter
umlauts, even delete them (no visual artefacts) and everything is fine
after login. So only the first call to getty is vulnerable to this
effect. If I exceed
Anyway this is more general problem but not shadow bug (it is about UTF8
support, not about umlauts), so probably nothing should be done in
shadow. But some program should set that flag *before* login run and
*all* terminal emulators should set this flag when run in UTF-8 locale
:(
The
28 вересня 2005 о 06:46 +0200 Christian Perrier написав(-ла):
Anyway this is more general problem but not shadow bug (it is about UTF8
support, not about umlauts), so probably nothing should be done in
shadow. But some program should set that flag *before* login run and
*all* terminal
On Tue, 27 Sep 2005, Eugeniy Meshcheryakov wrote:
27 вересня 2005 о 18:36 +0200 Tomasz Kłoczko написав(-ла):
Eugeniy this is incorrect way .. better will be use IUTF8 atribute
I know that it is incorrect, i sent this patch only as demonstration of
the problem.
from tty level
Hello Christian,
On Wed, Sep 28, 2005 at 06:46:16AM +0200, Christian Perrier wrote:
Anyway this is more general problem but not shadow bug (it is about UTF8
support, not about umlauts), so probably nothing should be done in
Well, I think there are two issues here: one about UTF8 support which
tags 221290 confirmed
thanks
On Tue, Sep 27, 2005 at 06:13:25PM +0200, Helge Kreutzmann wrote:
Well, I don't have an all caps afterwards.
Surely, that's completely another thing, for
historical reasons BTW.
I just checked (on Sarge)
the same, on linux console, vesafb, UA/UTF-8 keymap
When
Right?
No. Please tag it help if you do not know the cause. I tried to have
a look at the sources, but frankly I don't know how login sets console
properties, hence I did not find the problematic point.
Well, it seems that my co-maintainers have a better idea than me about
this problem.
Hi!
After a small, fast and simple check I conclude that
the issue with setting cs7 on terminal after entering
non-ascii letters into login: prompt is really a
probem with /sbin/getty (util-linux pkg).
On Wed, Sep 28, 2005 at 07:49:14PM +0300, Alexander Gattin wrote:
When I run stty -a in a
Hello Alexander,
On Wed, Sep 28, 2005 at 10:48:46PM +0300, Alexander Gattin wrote:
After a small, fast and simple check I conclude that
the issue with setting cs7 on terminal after entering
non-ascii letters into login: prompt is really a
probem with /sbin/getty (util-linux pkg).
Confirmed
Hi!
On Wed, Sep 28, 2005 at 10:46:23PM +0200, Helge Kreutzmann wrote:
Hello Alexander,
On Wed, Sep 28, 2005 at 10:48:46PM +0300, Alexander Gattin wrote:
After a small, fast and simple check I conclude that
the issue with setting cs7 on terminal after entering
Probably istrip (clear 8th bit
On Tue, 27 Sep 2005, Eugeniy Meshcheryakov wrote:
27 вересня 2005 о 07:38 +0200 Christian Perrier написав(-ла):
I was waiting for upstream resync to deal with this bug report but it
still seems to be here.
When entering high-ascii characters at the login prompt (usually by
mistake),
27 вересня 2005 о 18:36 +0200 Tomasz Kłoczko написав(-ла):
Eugeniy this is incorrect way .. better will be use IUTF8 atribute
I know that it is incorrect, i sent this patch only as demonstration of
the problem.
from tty level description. Example from my system:
$ stty -a | grep utf
-iuclc
12 matches
Mail list logo
