From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Houder <houder@xs4all.nl>
Cc: cygwin@cygwin.com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Date: Wed, 20 Feb 2019 21:50:00 -0000 [thread overview]
Message-ID: <20190220214108.GZ4256@calimero.vinschen.de> (raw)
In-Reply-To: <0a2366b9de0f65ed912d41c2ee040f4a@smtp-cloud8.xs4all.net>
[-- Attachment #1: Type: text/plain, Size: 2365 bytes --]
On Feb 20 22:35, Houder wrote:
> On Wed, 20 Feb 2019 21:25:36, Corinna Vinschen wrote:
>
> > 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.
>
> Understood.
>
> > For completeness sake I started sshd under SYSTEM as wel as under
> > cyg_server account and every time it just worked.
>
> Mine runs under cyg_server
>
> > 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,[...]
>
> Understood. And not the problem at my side. Also I am using local
> accounts.
>
> Failure starts w/ cygwin1-20190126 ... 0124 works ...
>
> Your commits on 0126:
>
> 2019-01-26 Corinna Vinschen Cygwin: seteuid: use Kerberos/MsV1_0 S4U authentication...
> 2019-01-26 Corinna Vinschen Cygwin: uname: Raise size of utsname fields and revamp...
> 2019-01-26 Corinna Vinschen Cygwin: netdb.h: fix __GNU_VISIBLE tests
> 2019-01-26 Corinna Vinschen Cygwin: create_token: Return NULL, not INVALID_HANDLE_...
> 2019-01-26 Corinna Vinschen Cygwin: syscalls.cc: fix formatting
> 2019-01-26 Corinna Vinschen Cygwin: lsaauth: Drop outdated test for loading Secur32.dll
>
> Last commit:
>
> Cygwin: seteuid: use Kerberos/MsV1_0 S4U authentication by default
>
> - This simple and official method replaces cyglsa and "create token"
> methods. No network share access, same as before.
>
> - lsaauth and create_token are disabled now. If problems crop up,
> they can be easily reactivated. If no problems crop up, they
> can be removed in a while, together with the lsaauth subdir.
>
> - Bump Cygwin version to 3.0.
>
> -----
>
> Perhaps I missed something in the last couple of month. Did I have to change
> something in the setup of openssh?
I really don't know, this all works fine for me. Try switching the
account starting sshd from cyg_server to LocalSystem and change
ownership of all files /etc/ssh* to SYSTEM.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-20 21:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19759126.568100.1550686604174.ref@mail.yahoo.com>
2019-02-20 18:53 ` James R. Phillips via cygwin
2019-02-20 19:04 ` scowles
2019-02-20 19:47 ` Bill Stewart
2019-02-20 20:01 ` scowles
2019-02-20 20:25 ` Houder
2019-02-20 21:27 ` Corinna Vinschen
2019-02-20 21:34 ` Andy Moreton
2019-02-20 21:39 ` Corinna Vinschen
2019-02-20 22:13 ` scowles
2019-02-20 21:50 ` Houder
2019-02-20 22:38 ` Corinna Vinschen
2019-02-20 22:44 ` Corinna Vinschen
2019-02-21 11:43 ` Corinna Vinschen
2019-02-21 16:01 ` Houder
2019-02-23 19:15 ` Cary Lewis
2019-02-24 6:58 ` Cary Lewis
2019-09-15 6:45 ` Basin Ilya
2019-09-15 7:07 ` Basin Ilya
2019-02-20 21:35 ` Bill Stewart
2019-02-20 21:37 ` Houder
2019-02-20 21:50 ` Corinna Vinschen [this message]
2019-02-20 22:08 ` Houder
2019-02-20 22:32 ` Houder
2019-02-20 22:43 ` Corinna Vinschen
2019-02-21 5:16 ` Houder
2019-02-20 22:36 ` scowles
2019-02-20 23:08 ` Corinna Vinschen
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=20190220214108.GZ4256@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=houder@xs4all.nl \
/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).