Bug#221290: [OBORONA-SPAM] [?? Probable Spam] Bug#221290: [Pkg-shadow-devel] Bug#221290: Bug #221290 still here: screen garbled after entering high-ascii characters at login prompt

[Helge Kreutzmann]

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 the "maximum number of tries", the next getty is
back to the "old" behaviour, with visual artefacts and so on.

On Thu, Sep 29, 2005 at 12:52:47AM +0300, Alexander Gattin wrote:
> 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 of input characters)
> is more relevant to the problem than cs7... I'm not a
> TTY guru.

Yes. I know this from a different bug still present in the BTS, where
I have to manually set -istrip.

> I have prepared a wrapper script, to work around the
> problem with getty. Currently it just sets tty to some
> 'sane' state.
> 
> Citing /root/stty-cs8-login.sh:
> > #!/bin/bash --norc
> > stty cs8 -parenb -parodd -cstopb -inpck -istrip
> > exec /bin/login $@
> 
> Please, try it to see whether it fixes your problem
> or not. The script should be given to getty instead

It works as intended. The visual artefact on the first prompt remains,
of course, but the shell behaves as expected (i.e., vim behaves
correctly). So I guess the next step would be to find out where the
default settings are stored, so that the wrapper could retrieve the
default set instead of hard coded corrections?

> Intrinsics are very simple, indeed :) -- getty prints
> /etc/issue and "login:" prompt after that.

Yep, reading the man page of getty helps (I thought I had to read some
scripts of sources)

So this testing clearly shows that this is a getty issue. Getty sees
the 8 bit character and decides, to change the tty-settings
accordingly (for some reason). It only runs this detection on the
first login-prompt displayed by itself. A side effect is the distorted
printing of the backspace operation.

Should we reassign to getty?

Greetings

           Helge
-- 
Dr. Helge Kreutzmann, Dipl.-Phys.           Helge.Kreutzmann at itp.uni-hannover.de
                       gpg signed mail preferred 
    64bit GNU powered                  http://www.itp.uni-hannover.de/~kreutzm
          Help keep free software "libre": http://www.ffii.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/attachments/20050929/3e50b2d8/attachment.pgp