From: Karel Zak <kzak@redhat.com>
To: "Dr. Werner Fink" <werner@suse.de>, util-linux@vger.kernel.org
Subject: agetty and special chars @ and #
Date: Wed, 7 Nov 2012 17:58:59 +0100 [thread overview]
Message-ID: <20121107165859.GD4383@x2.net.home> (raw)
Hi Werner,
agetty in get_logname() interprets '@' and '#' as a special chars
(see man page or the code for more details).
The problem is that we already have crazy users who want to use AD
(access domain) usernames in format user@domain on serial line or
console.
Yeah, I know that char '@' is not between allowed username chars
(POSIX 3.429), but do we really need to support the spacial
interpretation of the @ and # chars?
I think it's old confusing legacy. Objections?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next reply other threads:[~2012-11-07 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 16:58 Karel Zak [this message]
2012-11-12 10:04 ` agetty and special chars @ and # Dr. Werner Fink
2012-11-12 13:29 ` Karel Zak
2012-11-14 14:27 ` Dr. Werner Fink
2012-11-16 10:14 ` Karel Zak
2012-11-16 12:47 ` Lennart Poettering
2012-11-16 13:05 ` Karel Zak
2012-11-20 0:47 ` Lennart Poettering
2012-11-20 9:26 ` [util-linux] " Dr. Werner Fink
2012-11-20 16:59 ` Lennart Poettering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121107165859.GD4383@x2.net.home \
--to=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
--cc=werner@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).