Re: bin/49297: openssh update broke sshd

[<Paul_Koning%Dell.com@localhost>]

The following reply was made to PR bin/49297; it has been noted by GNATS.

From: <Paul_Koning%Dell.com@localhost>
To: <christos%zoulas.com@localhost>
Cc: <gnats-bugs%NetBSD.org@localhost>, <gnats-admin%netbsd.org@localhost>,
	<netbsd-bugs%netbsd.org@localhost>
Subject: Re: bin/49297: openssh update broke sshd
Date: Tue, 21 Oct 2014 14:44:36 +0000

 On Oct 21, 2014, at 9:02 AM, Christos Zoulas <christos%zoulas.com@localhost> wrote:
 
 > On Oct 21,  6:25am, martin%NetBSD.org@localhost (martin%NetBSD.org@localhost) wrote:
 > -- Subject: bin/49297: openssh update broke sshd
 >=20
 > | ...
 > | After updating this machine to -current as of yesterday (i.e. with the =
 brand
 > | new openssh imported) I can't log into it from some windows machines
 > | any more:
 > |=20
 > | Oct 21 08:16:19 whoever-brings-the-night sshd[1610]: fatal: no matching=
  cipher found: client aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,twofish-=
 cbc,arcfour server aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm%openssh.com@localhost,=
 aes256-gcm%openssh.com@localhost,chacha20-poly1305%openssh.com@localhost [preauth]
 > |=20
 >=20
 > Yes, they removed a whole bunch of ciphers because they are not supportin=
 g
 > them anymore. We could either consider bringing them back, or you need to
 > upgrade your windows ssh to something newer.
 
 I can understand that for oddballs like cast and the fishes, but it isn=92t=
  obvious why AES would be removed.
 
 	paul