Corinna Vinschen wrote:
> This should fix your problem...
Fixed!
Many thanks,
Angelo.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http:/
On Mar 12 09:20, Angelo Graziosi wrote:
> I contacted the administrator of 'hostname' and he confirmed that
> 'hostname' accepts only the option '-1' with ssh (even if it would be
> better to use -2)!
>
> Using '-2' toward another machine, it works!
>
> So the conclusion is that openssh-4.6p1 see
Corinna Vinschen wrote:
> I suggest to take the opportunity to switch to protocol 2 which is
> the better and safer protocol anyway.
I wrote:
> I have tried, but :
>
> $ ssh -2 [EMAIL PROTECTED]
> Protocol major versions differ: 2 vs. 1
>
> (openssh-4.5p1-1 with -2 gives the some result)
>
> W
Brian Dessent wrote:
What kind of backwater system is this that doesn't have support for SSH
v2? Version 2 has been the default for many, many years, and version 1
is very deprecated/insecure/etc. Normally you shouldn't even have to
specify the version, as the client should negotiate it with t
Brian Dessent wrote:
> What kind of backwater system is this that doesn't have support for SSH
> v2? Version 2 has been the default for many, many years, and version 1
> is very deprecated/insecure/etc. Normally you shouldn't even have to
> specify the version, as the client should negotiate it
On Mar 8 09:42, Brian Dessent wrote:
> Angelo Graziosi wrote:
>
> > > I suggest to take the opportunity to switch to protocol 2 which is
> > > the better and safer protocol anyway.
> >
> > I have tried, but :
> >
> > $ ssh -2 [EMAIL PROTECTED]
> > Protocol major versions differ: 2 vs. 1
> >
>
Angelo Graziosi wrote:
> > I suggest to take the opportunity to switch to protocol 2 which is
> > the better and safer protocol anyway.
>
> I have tried, but :
>
> $ ssh -2 [EMAIL PROTECTED]
> Protocol major versions differ: 2 vs. 1
>
> (openssh-4.5p1-1 with -2 gives the some result)
What kind
Corinna Vinschen wrote:
> I suggest to take the opportunity to switch to protocol 2 which is
> the better and safer protocol anyway.
I have tried, but :
$ ssh -2 [EMAIL PROTECTED]
Protocol major versions differ: 2 vs. 1
(openssh-4.5p1-1 with -2 gives the some result)
While
$ ssh [EMAIL PROT
On Mar 8 16:36, Angelo Graziosi wrote:
>
> I have always used ssh in this way:
>
> $ ssh -1 [EMAIL PROTECTED]
>
> but after updating to this version:
>
>
> $ ssh -1 [EMAIL PROTECTED]
> Disconnecting: Corrupted check bytes on input.
This looks like an upstream bug. Connecting with protocol v
I have always used ssh in this way:
$ ssh -1 [EMAIL PROTECTED]
but after updating to this version:
$ ssh -1 [EMAIL PROTECTED]
Disconnecting: Corrupted check bytes on input.
I have tried more than one host with the same result.
I have also deleted ~/.ssh so that it is regenerated but same re
10 matches
Mail list logo