From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83614 invoked by alias); 26 Jan 2019 19:05:15 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 83546 invoked by uid 89); 26 Jan 2019 19:05:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=BAYES_05,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=separately, H*F:D*yandex.ru, english, H*UA:Bat! X-HELO: forward102p.mail.yandex.net Received: from forward102p.mail.yandex.net (HELO forward102p.mail.yandex.net) (77.88.28.102) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 26 Jan 2019 19:05:12 +0000 Received: from mxback6o.mail.yandex.net (mxback6o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::20]) by forward102p.mail.yandex.net (Yandex) with ESMTP id 0B36E1D40384; Sat, 26 Jan 2019 22:05:10 +0300 (MSK) Received: from smtp1o.mail.yandex.net (smtp1o.mail.yandex.net [2a02:6b8:0:1a2d::25]) by mxback6o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id uP5MpTn41J-53i4hcKE; Sat, 26 Jan 2019 22:05:03 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1548529503; bh=bDVoYs5Ml0sm10r77lq3No1yv/7KanTAQp67POIL0ZM=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=uuMKNzA4GgPL/Msy2D1R4wG2FLmpBDR3/O7nodVd/hqN6axoVP7fYfsTG7gs9DZVp mAO7Be5S+CxhDuiS0XgylJEx79c4XcVNrGtr9S62nyqvCQHmNvOw4f263pPcL/0YUi 0Bta2ii+4bmJhnwvszfUqrahzWiTDr1FxnEbq0Ko= Authentication-Results: mxback6o.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by smtp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id JVyZgkgG5y-52guEUC3; Sat, 26 Jan 2019 22:05:03 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Sat, 26 Jan 2019 19:02:03 -0000 Date: Sat, 26 Jan 2019 19:05:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <1105935204.20190126220203@yandex.ru> To: Stefan Baur , cygwin@cygwin.com Subject: Re: sshd permits logon using disabled user? In-Reply-To: <51ded8a7-ffc0-c1b0-8bb6-8d2f5870ec68@baur-itcs.de> References: <20190124154533.GK2802@calimero.vinschen.de> <2b348ac3-63d1-2cd3-430d-2568d650a583@baur-itcs.de> <20190124155918.GL2802@calimero.vinschen.de> <51ded8a7-ffc0-c1b0-8bb6-8d2f5870ec68@baur-itcs.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00237.txt.bz2 Greetings, Stefan Baur! > 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), Unfortunately, that's not possible. -- With best regards, Andrey Repin Saturday, January 26, 2019 22:01:42 Sorry for my terrible english... -- 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