public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Problem with sshd on W7 with 32bit cygwin 3.0
@ 2019-02-18 11:05 Enrico Forestieri
  2019-02-18 14:28 ` Corinna Vinschen
  0 siblings, 1 reply; 6+ messages in thread
From: Enrico Forestieri @ 2019-02-18 11:05 UTC (permalink / raw)
  To: cygwin

After upgrading to cygwin 3.0.0 (32bit version) on W7 64bit, it is
not possible to connect using ssh. The returned error is something
like "Connection closed by x.x.x.x port 22".

I also tried the 2019-02-18 snapshot without success.
However, simply downgrading to 2.11.2 fixes the issue.

This issue does not seem to affect 64bit cygwin versions on W10.

-- 
Enrico

--
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problem with sshd on W7 with 32bit cygwin 3.0
  2019-02-18 11:05 Problem with sshd on W7 with 32bit cygwin 3.0 Enrico Forestieri
@ 2019-02-18 14:28 ` Corinna Vinschen
  2019-02-18 16:20   ` Enrico Forestieri
  0 siblings, 1 reply; 6+ messages in thread
From: Corinna Vinschen @ 2019-02-18 14:28 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

On Feb 18 11:58, Enrico Forestieri wrote:
> After upgrading to cygwin 3.0.0 (32bit version) on W7 64bit, it is
> not possible to connect using ssh. The returned error is something
> like "Connection closed by x.x.x.x port 22".
> 
> I also tried the 2019-02-18 snapshot without success.
> However, simply downgrading to 2.11.2 fixes the issue.

I tested this myself and from what I can tell, Microsoft didn't
implement S4U for local accounts on WOW64 on older OSes.  If I
start a 32 bit sshd from an Windows 7 64 bit WOW64 environment,
then domain accounts work fine using kerberos S4U, but for local
accounts with MsV1_0 S4U the underlying Windows function returns
STATUS_INVALID_PARAMETER.

Note that this works fine in Windows 7 64 bit with 64 bit Cygwin.  It
seems only older WOW64 environments (maybe even only in W7) didn't
implement this.

Two workarounds for now:

- Start sshd as 64 bit Cygwin process.
- Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problem with sshd on W7 with 32bit cygwin 3.0
  2019-02-18 14:28 ` Corinna Vinschen
@ 2019-02-18 16:20   ` Enrico Forestieri
  2019-02-18 23:36     ` Corinna Vinschen
  0 siblings, 1 reply; 6+ messages in thread
From: Enrico Forestieri @ 2019-02-18 16:20 UTC (permalink / raw)
  To: cygwin

On Mon, Feb 18, 2019 at 03:11:11PM +0100, Corinna Vinschen wrote:
> 
> Two workarounds for now:
> 
> - Start sshd as 64 bit Cygwin process.
> - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3

Thank you. The second method above worked. This is a private network,
so that is Ok.

-- 
Enrico

--
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problem with sshd on W7 with 32bit cygwin 3.0
  2019-02-18 16:20   ` Enrico Forestieri
@ 2019-02-18 23:36     ` Corinna Vinschen
  2019-02-19 11:44       ` Enrico Forestieri
  0 siblings, 1 reply; 6+ messages in thread
From: Corinna Vinschen @ 2019-02-18 23:36 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

On Feb 18 17:04, Enrico Forestieri wrote:
> On Mon, Feb 18, 2019 at 03:11:11PM +0100, Corinna Vinschen wrote:
> > 
> > Two workarounds for now:
> > 
> > - Start sshd as 64 bit Cygwin process.
> > - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3
> 
> Thank you. The second method above worked. This is a private network,
> so that is Ok.

I uploaded new developer snapshots with fixes for this problem:
https://cygwin.com/snapshots/  Please give it a try. 


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problem with sshd on W7 with 32bit cygwin 3.0
  2019-02-18 23:36     ` Corinna Vinschen
@ 2019-02-19 11:44       ` Enrico Forestieri
  2019-02-19 13:06         ` Corinna Vinschen
  0 siblings, 1 reply; 6+ messages in thread
From: Enrico Forestieri @ 2019-02-19 11:44 UTC (permalink / raw)
  To: cygwin

On Mon, Feb 18, 2019 at 09:54:50PM +0100, Corinna Vinschen wrote:
> On Feb 18 17:04, Enrico Forestieri wrote:
> > On Mon, Feb 18, 2019@03:11:11PM +0100, Corinna Vinschen wrote:
> > > 
> > > Two workarounds for now:
> > > 
> > > - Start sshd as 64 bit Cygwin process.
> > > - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3
> > 
> > Thank you. The second method above worked. This is a private network,
> > so that is Ok.
> 
> I uploaded new developer snapshots with fixes for this problem:
> https://cygwin.com/snapshots/  Please give it a try. 

Thanks. I can confirm that with this snaspshot sshd works fine without
the need for the workaround.

-- 
Enrico

--
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problem with sshd on W7 with 32bit cygwin 3.0
  2019-02-19 11:44       ` Enrico Forestieri
@ 2019-02-19 13:06         ` Corinna Vinschen
  0 siblings, 0 replies; 6+ messages in thread
From: Corinna Vinschen @ 2019-02-19 13:06 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

On Feb 19 11:30, Enrico Forestieri wrote:
> On Mon, Feb 18, 2019 at 09:54:50PM +0100, Corinna Vinschen wrote:
> > On Feb 18 17:04, Enrico Forestieri wrote:
> > > On Mon, Feb 18, 2019@03:11:11PM +0100, Corinna Vinschen wrote:
> > > > 
> > > > Two workarounds for now:
> > > > 
> > > > - Start sshd as 64 bit Cygwin process.
> > > > - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3
> > > 
> > > Thank you. The second method above worked. This is a private network,
> > > so that is Ok.
> > 
> > I uploaded new developer snapshots with fixes for this problem:
> > https://cygwin.com/snapshots/  Please give it a try. 
> 
> Thanks. I can confirm that with this snaspshot sshd works fine without
> the need for the workaround.

Thanks for testing!


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-02-19 11:44 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-18 11:05 Problem with sshd on W7 with 32bit cygwin 3.0 Enrico Forestieri
2019-02-18 14:28 ` Corinna Vinschen
2019-02-18 16:20   ` Enrico Forestieri
2019-02-18 23:36     ` Corinna Vinschen
2019-02-19 11:44       ` Enrico Forestieri
2019-02-19 13:06         ` Corinna Vinschen

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).