public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: James Carter <james.carter@bytemark.co.uk>
To: 705483@bugs.debian.org
Subject: Bug#705483: xfsprogs: xfs_quota misinterprets usernames with leading digits
Date: Tue, 16 Apr 2013 09:17:21 +0100	[thread overview]
Message-ID: <516D0911.5080408@bytemark.co.uk> (raw)
In-Reply-To: <516C25AC.60506@sgi.com>

On 15/04/13 17:07, Rich Johnston wrote:
>
> I don't think this is a bug, username must begin with a character 
> (unless you created the user using NIS or adduser --force-badname).

My understanding that this is a recommendation rather than a 
requirement. useradd(8) has the following to say:

        On Debian, the only constraints are that usernames must neither 
start
        with a dash ('-') nor contain a colon (':') or a whitespace 
(space: '
        ', end of line: '\n', tabulation: '\t', etc.). Note that using a 
slash
        ('/') may break the default algorithm for the definition of the 
user's
        home directory.

In any case, I'd still consider it a bug that trailing non-numeric 
characters were just silently ignored.

-- 
James Carter                                           Bytemark Hosting
                                              http://www.bytemark.co.uk/
                                               tel: +44 (0) 1904 890 890

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-04-16  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 14:46 Bug#705483: xfsprogs: xfs_quota misinterprets usernames with leading digits James Carter
2013-04-15 16:07 ` Rich Johnston
2013-04-16  8:17   ` James Carter [this message]
2013-04-16 12:29     ` Rich Johnston
2013-04-23 13:02 ` Rich Johnston

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=516D0911.5080408@bytemark.co.uk \
    --to=james.carter@bytemark.co.uk \
    --cc=705483@bugs.debian.org \
    /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