X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=jGpUXGZ
	jlMVtglawo9dJJ9bav/9S9H+6o9mZsmxyImPN8FZT3VFb7S7cq2iyAPWUhjCmEmm
	S7/twCrXYvnjusjtO/1gXURiDXrFHOJctTx6Zqoeig6ONPuN8ecNbZ98dqwaARdU
	Ryzd+Sof9zyxK1zv8EAjBFTLI7TUPariCwlQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; s=default; bh=63XKsioaWJj1J
	/LnV/PEhEoEbQ4=; b=Mvm9tU/A3kOM95LWqo0wHhom6n/ABO7QMTHIRFMtHrXi4
	78bR/IY57EhdsRmjMCPU7h1Afiu9Ctip0rPDyv32p7oGQzpW5cBVLGcTftx5g5eS
	0Si3/+BQ9eNx8cro8AGW/gUXjjFyCPCbElHs1Ccj+qPne9Ngz4D80iuuuPSF2o=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=_the
X-HELO:	mout.gmx.com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/simple; d=mail.com; s=dbd5af2cbaf7; t=1548430464; bh=XnRXD6bi8pW4TR088LcX6zMmB9n8nw9UNmenAXWae7g=; h=X-UI-Sender-Class:References:In-Reply-To:From:Date:Subject:To; b=4oA3jtyccBXW0NxHaW+Xd0nzArq14INk0+k4E+t9Awa6fWSBawMMeHFPTQ/exLUWy LTo91A8/LkUL0aiQbHfFK7gA21zny4pq5DhZukQzZvh8YR6LBC1szXuS4/nncLOGb7 yH3bATOV5kvlop0qJ/Y1oyX9zV5CwvaohBkl6Mog=
X-UI-Sender-Class:	214d933f-fd2f-45c7-a636-f5d79ae31a79
MIME-Version:	1.0
References:	<1690850474 DOT 834980 DOT 1548391349102 DOT ref AT mail DOT yahoo DOT com> <1690850474 DOT 834980 DOT 1548391349102 AT mail DOT yahoo DOT com> <d6f98cbc-bd2f-1c13-98bb-7ef42c000115 AT baur-itcs DOT de>
In-Reply-To:	<d6f98cbc-bd2f-1c13-98bb-7ef42c000115@baur-itcs.de>
From:	Bill Stewart <bstewart AT iname DOT com>
Date:	Fri, 25 Jan 2019 08:34:09 -0700
Message-ID:	<CANV9t=RKVWPfiqNMbnSgevTBvm8S1G-oFWK3BEisdgaSGz2OzA@mail.gmail.com>
Subject:	Re: sshd permits logon using disabled user?
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

On Fri, Jan 25, 2019 at 3:36 AM Stefan Baur <X2Go-ML-1 AT baur-itcs DOT 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

- Raw text -