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
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.c
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
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.
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, si
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 issu
6 matches
Mail list logo