public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stefan Baur <X2Go-ML-1@baur-itcs.de>
To: cygwin@cygwin.com
Subject: Re: sshd permits logon using disabled user?
Date: Thu, 24 Jan 2019 17:01:00 -0000	[thread overview]
Message-ID: <03a080c3-903e-ac05-fdaa-95dc0510bd08@baur-itcs.de> (raw)
In-Reply-To: <20190124163612.GM2802@calimero.vinschen.de>


[-- Attachment #1.1: Type: text/plain, Size: 1656 bytes --]

Am 24.01.19 um 17:36 schrieb Corinna Vinschen:
>> If an admin can lock out an account (separately from disabling it
>> entirely), say, by setting an initial password, checking the "user must
>> change password on first login", and also checking "user is not allowed
>> to change password" simultaneously (if that's possible), or, say, by
>> just setting a random password without telling it to anyone ever,
>> followed by firing so many login attempts at the account that it gets
>> locked out, then telling them apart and treating locked out accounts
>> differently would make sense, IMO.

> This description sounds extremly artificial to me.

> We should work under
> the assumption that the admin is the good guy.

Uh, where did I imply anything else?


>  Usually a user locks
> itself out, or is locked out by a malicious login attempt.  The admin
> can only define rules for locking out, other than that she can only
> remove the "account locked" flag.

The methods listed above, well, at least the "brute force" one, would
work for intentionally creating an account that is locked out, but not
disabled - as a good guy admin.

And the reason for doing so would be the same as running "passwd -l
username" on Linux - You don't want your users to log in with a
password, because you consider that too insecure - instead, you want
them to use the (hopefully passphrase-protected) SSH key file.

Kind Regards,
Stefan Baur

-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2019-01-24 17:01 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 13:28 Bill Stewart
2019-01-24 15:45 ` Corinna Vinschen
2019-01-24 15:51   ` Stefan Baur
2019-01-24 15:59     ` Corinna Vinschen
2019-01-24 16:16       ` Stefan Baur
2019-01-24 16:36         ` Corinna Vinschen
2019-01-24 17:01           ` Stefan Baur [this message]
2019-01-26 19:05         ` Andrey Repin
2019-01-24 16:49   ` Bill Stewart
2019-01-24 20:23     ` Corinna Vinschen
2019-01-24 20:37       ` Bill Stewart
2019-01-25 16:56         ` Corinna Vinschen
2019-01-24 17:52   ` Bill Stewart
2019-01-24 17:58     ` Stefan Baur
2019-01-24 18:13       ` Bill Stewart
2019-01-24 19:17         ` Wayne Davison
2019-01-24 19:22           ` Stefan Baur
2019-01-26 19:20     ` Andrey Repin
     [not found] <1690850474.834980.1548391349102.ref@mail.yahoo.com>
2019-01-25  4:42 ` matthew patton via cygwin
2019-01-25 10:36   ` Stefan Baur
2019-01-25 15:34     ` Bill Stewart
2019-01-25 17:48       ` Stephen Paul Carrier
2019-01-25 18:03         ` Bill Stewart
2019-01-27 17:48           ` Sam Edge (Cygwin)
2019-01-27 22:10             ` Corinna Vinschen
2019-01-28 13:35               ` Sam Edge
2019-01-28  9:59           ` Corinna Vinschen
2019-01-28 15:02             ` Bill Stewart
2019-01-28 16:52               ` Corinna Vinschen
2019-01-28 17:19                 ` Bill Stewart
2019-01-28 18:39                   ` Corinna Vinschen
2019-01-28 20:14                     ` Bill Stewart
2019-01-28 21:50                       ` Bill Stewart
2019-01-28 22:24                         ` Bill Stewart
2019-01-29 11:57                         ` Corinna Vinschen
2019-01-29 12:12                           ` Corinna Vinschen
2019-01-29 17:05                             ` Corinna Vinschen
2019-01-29 18:18                               ` Bill Stewart
2019-01-29 18:30                                 ` Corinna Vinschen

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=03a080c3-903e-ac05-fdaa-95dc0510bd08@baur-itcs.de \
    --to=x2go-ml-1@baur-itcs.de \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).