Date: Fri, 01 Mar 2013 20:44:53 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Mike Tancsa <mike@sentex.net> Cc: stable@freebsd.org, svn-src-stable-9@freebsd.org Subject: Re: svn commit: r247485 - in stable/9: crypto/openssh crypto/openssh/openbsd-compat secure/lib/libssh secure/usr.sbin/sshd Message-ID: <867glqsy4q.fsf@ds4.des.no> In-Reply-To: <5130E9F1.6050308@sentex.net> (Mike Tancsa's message of "Fri, 01 Mar 2013 12:48:33 -0500") References: <201302281843.r1SIhoaq004371@svn.freebsd.org> <5130D8E0.3020605@sentex.net> <5130E9F1.6050308@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Tancsa <mike@sentex.net> writes: > OK, so it looks like something to do with hardware crypto. If I unload > aesni.ko and restart sshd, it works, even with aes128-cbc which I guess > it was trying to use cryptodev Are you sure this was due to the OpenSSH update, and not the OpenSSL update a few days ago? Can you try to roll back to r247484? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867glqsy4q.fsf>