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 15:51:00 -0000 [thread overview]
Message-ID: <2b348ac3-63d1-2cd3-430d-2568d650a583@baur-itcs.de> (raw)
In-Reply-To: <20190124154533.GK2802@calimero.vinschen.de>
[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]
Am 24.01.19 um 16:45 schrieb Corinna Vinschen:
>> In the shell, logged on as the disabled user, the 'whoami' command returns
>> the name of the disabled user.
>>
>> This seems unexpected and not good.
>>
>> Why does sshd allow logon for a disabled user?
> Because the underlying Cygwin function responsible for changing the user
> account only checks if the account exists. It does not check for any of
> the flags in the user DB. Yet.
>
> I pushed a patch to disallow changing the user account to a disabled or
> locked out account.
I would like to point out that on Linux, you can disable an account's
password ("password -l username" / "usermod -L username"), and still log
in using an SSH key pair. This is intentional and different to
disabling an account entirely ("usermod -e 1 username" combined with the
above).
So I guess, the question is if there's a way to make Cygwin act similar
to this - maybe if you can tell disabled vs. locked out apart, allow SSH
key pair logins when locked out, but not when disabled?
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 --]
next prev parent reply other threads:[~2019-01-24 15:51 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 [this message]
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
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=2b348ac3-63d1-2cd3-430d-2568d650a583@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).