Re: svn commit: r295367 - in stable/10: crypto/openssh crypto/openssh/contrib crypto/openssh/contrib/caldera crypto/openssh/contrib/cygwin crypto/openssh/contrib/redhat crypto/openssh/contrib/suse cry

On 3/3/2016 1:46 AM, Dag-Erling Smørgrav wrote: > Mike Tancsa writes: >> I noticed on a server that I updated on Friday that incorporates >> r295367, some lightweight clients that were using aes128-cbc are now >> failing to connect. Is this a planned change ? If so, perhaps a

Re: svn commit: r295367 - in stable/10: crypto/openssh crypto/openssh/contrib crypto/openssh/contrib/caldera crypto/openssh/contrib/cygwin crypto/openssh/contrib/redhat crypto/openssh/contrib/suse cry

Mike Tancsa writes: > I noticed on a server that I updated on Friday that incorporates > r295367, some lightweight clients that were using aes128-cbc are now > failing to connect. Is this a planned change ? If so, perhaps a heads > up in UPDATING ? Please file a bug and send me

Re: svn commit: r295367 - in stable/10: crypto/openssh crypto/openssh/contrib crypto/openssh/contrib/caldera crypto/openssh/contrib/cygwin crypto/openssh/contrib/redhat crypto/openssh/contrib/suse cry

Hi, I noticed on a server that I updated on Friday that incorporates r295367, some lightweight clients that were using aes128-cbc are now failing to connect. Is this a planned change ? If so, perhaps a heads up in UPDATING ? e.g. from an older client ssh -c aes128-cbc