On Feb 20 21:01, Houder wrote: > On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote: > > > > i can confirm the same behaviours on a 3.0.0 system. i've done several > > checks > > and have been unable to find the source of the problem. ssh -vvv shows > > that the > > connection proceeds all the way through the connection process, sends the > > appropriate key tokens, then the server abruptly closes the connection. all > > accounts on the system show the same results. > > > > my 2.11.1 system, with identical ssh[d]_config files has no such problems. > > > > on both systems, all relevant files and directories have correct owners and > > permissions. > > Yes, failure for 3.0.0 (and 3.0.1); success for 2.11.2 > > Henri > > 64-@@ uname -a > CYGWIN_NT-6.1 Seven 3.0.1(0.338/5/3) 2019-02-20 10:19 x86_64 Cygwin > > 64-@@ tail /var/log/sshd.log > Server listening on 0.0.0.0 port 222. > seteuid 1004: Permission denied
Sorry guys, but I can't reproduce this problem at all. I tested ssh login on Vista, W7 and W10 1809, in each case on 64 bit and under WOW64. On all systems I can login with domain as well as local accounts. For completeness sake I started sshd under SYSTEM as wel as under cyg_server account and every time it just worked. The only reason for failing logins coming to mind is the case of the usernames. It must be written *exactly* as returned by `getent passwd'. I.e.: $ getent passwd | grep -i foo MACHINE+Foo:*:197608:197121:U-MACHINE\Foo,[...] You have to login like this: $ ssh MACHINE+Foo This will not work: $ ssh machine+foo Corinna -- Corinna Vinschen Cygwin Maintainer
signature.asc
Description: PGP signature
