login does not accept @ (at) and # (hash) characters
Bug #64299 reported by
Alexandros Papadopoulos
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| shadow (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: login
Typing @ in the username prompt results in the whole line clearing, while typing # results in a backspace.
Revision history for this message
| Ralph Corderoy (ralph-inputplus) wrote | #1 |
Revision history for this message
| Adam Niedling (krychek) wrote | #2 |
| Changed in shadow: | |
| status: | New → Fix Released |
To post a comment you must log in.
I'm not clear why you think this is a problem. Traditionally, the default erase and kill characters on Unix were # and @ respectively. That's because they were available when other keys, like backspace, may not be. They also used to be echoed, e.g. "ed /etv#c/passwd" was what would appear on the screen.
It seems that getty(8) recognises those characters regardless of the tty's settings:
$ sudo sh -c 'stty -a </dev/tty1'
speed 38400 baud; rows 25; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; start = ^Q;
...
This is documented in getty(8) in version 2.12r-17ubuntu of the util-linux package which contains getty.