Date: Fri, 01 Mar 2013 15:00:04 -0500 From: Mike Tancsa <mike@sentex.net> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> 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: <513108C4.10501@sentex.net> In-Reply-To: <867glqsy4q.fsf@ds4.des.no> References: <201302281843.r1SIhoaq004371@svn.freebsd.org> <5130D8E0.3020605@sentex.net> <5130E9F1.6050308@sentex.net> <867glqsy4q.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/1/2013 2:44 PM, Dag-Erling Smørgrav wrote: > 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? I didnt think openssl got updated on RELENG_9 ? http://svnweb.freebsd.org/base?view=revision&revision=247484 ---Mike > > DES -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?513108C4.10501>