From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: sshd permits logon using disabled user?
Date: Fri, 25 Jan 2019 15:34:00 -0000 [thread overview]
Message-ID: <CANV9t=RKVWPfiqNMbnSgevTBvm8S1G-oFWK3BEisdgaSGz2OzA@mail.gmail.com> (raw)
In-Reply-To: <d6f98cbc-bd2f-1c13-98bb-7ef42c000115@baur-itcs.de>
On Fri, Jan 25, 2019 at 3:36 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
> Not on Linux (and possibly other Unices). There, it's perfectly valid
> to disable an account's password login (both locally and remote), but to
> at the same time allow ssh key file based logins for the same account.
But disabling _password login_ is an entirely separate issue from
disabling _the account itself_.
Before the fix, it was possible to log on to sshd using a disabled (or
locked) account.
There should be _no_ scenario where it is possible to log on using a
disabled/locked account.
(To state the obvious: That's the whole point of having
disabled/locked out flags - so the account cannot be used to log on.)
Regards,
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-01-25 15:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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
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
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='CANV9t=RKVWPfiqNMbnSgevTBvm8S1G-oFWK3BEisdgaSGz2OzA@mail.gmail.com' \
--to=bstewart@iname.com \
--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).