Util-Linux package development
 help / color / mirror / Atom feed
From: Martin Pitt <martin.pitt@ubuntu.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: Karel Zak <kzak@redhat.com>,
	util-linux@vger.kernel.org, Werner Fink <werner@suse.de>
Subject: Re: sulogin: Don't ask for password when it is locked/disabled
Date: Tue, 26 May 2015 10:35:13 +0200	[thread overview]
Message-ID: <20150526083513.GO2947@piware.de> (raw)
In-Reply-To: <556348A0.9020206@gmail.com>

Hello Bruce,

Bruce Dubbs [2015-05-25 11:06 -0500]:
> Perhaps it's security by obscurity, but doesn't this tell a malicious user
> immediately that the account is locked and to move on to another user id to
> try?

Remote auth tools like ssh and SASL don't tell you that, they just say
"permission denied" (for pretty much this reason, I figure).

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

      reply	other threads:[~2015-05-26  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 14:01 sulogin: Don't ask for password when it is locked/disabled Karel Zak
2015-05-25 16:06 ` Bruce Dubbs
2015-05-26  8:35   ` Martin Pitt [this message]

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=20150526083513.GO2947@piware.de \
    --to=martin.pitt@ubuntu.com \
    --cc=bruce.dubbs@gmail.com \
    --cc=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