On Fri, Jan 25, 2019 at 08:34:09AM -0700, Bill Stewart wrote: > On Fri, Jan 25, 2019 at 3:36 AM Stefan Baur <x2go-m...@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.
There are different paths to access and to completely disable the account you need to close all of them. There are many reasons to disable some paths without disabling all paths and converting the switch that can disable one path to a switch that will disable all paths will break some setups and be less flexible. (As Stefan Baur is pointing out effectively.) To disable ssh logins really, instead of changing the way Cygwin works for everyone, you could do what UNIX/Linux admins do, something like moving the user .ssh folder to .ssh.disabled. Stephen Carrier Systems Administrator BEAR (Berkeley Evaluation & Assessment Research) Center Graduate School of Education University of California, Berkeley http://BEARcenter.Berkeley.EDU/ carr...@berkeley.edu -- 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
