Re: AESNI, /dev/crypto, and new OpenSSL

2018-12-21 Thread Alexey Dokuchaev
On Fri, Dec 21, 2018 at 01:10:07AM +0700, Alexey Dokuchaev wrote: > On Thu, Dec 20, 2018 at 09:33:41AM -0800, Freddie Cash wrote: > > On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote: > > > Had something got broken here, or I'm misunderstanding how this machinery > > > now works? > > > > St

Re: AESNI, /dev/crypto, and new OpenSSL

2018-12-20 Thread Alexey Dokuchaev
On Thu, Dec 20, 2018 at 09:33:41AM -0800, Freddie Cash wrote: > On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote: > > Had something got broken here, or I'm misunderstanding how this machinery > > now works? > > Start reading here: > > https://lists.freebsd.org/pipermail/freebsd-stable/2018

Re: AESNI, /dev/crypto, and new OpenSSL

2018-12-20 Thread Freddie Cash
On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote: > Had something got broken here, or I'm misunderstanding how this machinery > now works? > Start reading here: https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090195.html That thread covers this issue. :) Along with the

AESNI, /dev/crypto, and new OpenSSL

2018-12-20 Thread Alexey Dokuchaev
Hi there, For many years, OpenSSL was quite vocal about which hw-accelerated algos it can use: $ uname -UK 1200058 1200058 $ openssl version OpenSSL 1.0.2n-freebsd 7 Dec 2017 $ openssl engine -c -t (cryptodev) BSD cryptodev engine [RSA, DSA, DH] <<< word