Re: /dev/crypto not being used in 12-STABLE

2018-12-12 Thread Jung-uk Kim
On 18. 12. 7., Jung-uk Kim wrote: > On 18. 12. 7., Jeremy Chadwick wrote: >> https://github.com/openssl/openssl/pull/3744/files#diff-e4eb329834da3d36278b1b7d943b3bc9 >> >> *) Add devcrypto engine. This has been implemented against >> cryptodev-linux, >> then adjusted to work on FreeBSD 8.4

Re: /dev/crypto not being used in 12-STABLE

2018-12-07 Thread Jung-uk Kim
On 18. 12. 7., Jeremy Chadwick wrote: > On Fri, Dec 07, 2018 at 06:38:04PM -0500, Jung-uk Kim wrote: >> On 18. 12. 6., Jeremy Chadwick wrote: >>> I'm not subscribed to -stable. >>> >>> This is in response to jkim@'s messages here: >>> >>> https://lists.freebsd.org/pipermail/freebsd-stable/2018-Dece

Re: /dev/crypto not being used in 12-STABLE

2018-12-07 Thread Jeremy Chadwick
On Fri, Dec 07, 2018 at 06:38:04PM -0500, Jung-uk Kim wrote: > On 18. 12. 6., Jeremy Chadwick wrote: > > I'm not subscribed to -stable. > > > > This is in response to jkim@'s messages here: > > > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090202.html > > https://lists.free

Re: /dev/crypto not being used in 12-STABLE

2018-12-07 Thread Ian Lepore
On Fri, 2018-12-07 at 18:38 -0500, Jung-uk Kim wrote: > > So while OpenSSL now uses more of its own native C and assembly code > > (e.g. for AES-NI support), and that's certainly faster than all the > > overhead that cryptodev(4) brings with it (see jhb@'s post), I wonder: > >  > > 1. What happens

Re: /dev/crypto not being used in 12-STABLE

2018-12-07 Thread Jung-uk Kim
On 18. 12. 6., Jeremy Chadwick wrote: > I'm not subscribed to -stable. > > This is in response to jkim@'s messages here: > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090202.html > https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090202.html > > Based on wh

Re: /dev/crypto not being used in 12-STABLE

2018-12-07 Thread John Baldwin
On 12/6/18 4:19 PM, Konstantin Belousov wrote: > On Thu, Dec 06, 2018 at 04:48:35PM -0700, John Nielsen wrote: >> Is aesni(4) even required if all you want is userland acceleration? >> > No, it is not. Same for rdrand_rng(4), if an application uses hw random > source directly. To elaborate furthe

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread Jeremy Chadwick
I'm not subscribed to -stable. This is in response to jkim@'s messages here: https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090202.html https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090202.html Based on what I can tell, OpenSSL 1.1.1 or thereabouts removed th

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread Konstantin Belousov
On Thu, Dec 06, 2018 at 04:48:35PM -0700, John Nielsen wrote: > Is aesni(4) even required if all you want is userland acceleration? > No, it is not. Same for rdrand_rng(4), if an application uses hw random source directly. ___ freebsd-stable@freebsd.org

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread Jung-uk Kim
On 18. 12. 6., Jung-uk Kim wrote: > On 18. 12. 6., John Nielsen wrote: >>> On Dec 6, 2018, at 4:04 PM, Xin LI wrote: >>> >>> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: I have upgraded two physical machines from 11-STABLE to 12-STABLE recently (one is 12.0-PRERELEASE r3413

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread Jung-uk Kim
On 18. 12. 6., John Nielsen wrote: >> On Dec 6, 2018, at 4:04 PM, Xin LI wrote: >> >> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: >>> >>> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently >>> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r34139

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread John Nielsen
> On Dec 6, 2018, at 4:39 PM, John Baldwin wrote: > > On 12/6/18 3:24 PM, John Nielsen wrote: >>> On Dec 6, 2018, at 4:04 PM, Xin LI wrote: >>> >>> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: I have upgraded two physical machines from 11-STABLE to 12-STABLE recently (o

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread Xin LI
On Thu, Dec 6, 2018 at 3:24 PM John Nielsen wrote: > > > On Dec 6, 2018, at 4:04 PM, Xin LI wrote: > > > > On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: > >> > >> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently > >> (one is 12.0-PRERELEASE r341380 and the other

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread John Baldwin
On 12/6/18 3:24 PM, John Nielsen wrote: >> On Dec 6, 2018, at 4:04 PM, Xin LI wrote: >> >> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: >>> >>> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently >>> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread John Nielsen
> On Dec 6, 2018, at 4:04 PM, Xin LI wrote: > > On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: >> >> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently >> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I >> noticed today that neither ma

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread Xin LI
On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: > > I have upgraded two physical machines from 11-STABLE to 12-STABLE recently > (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I > noticed today that neither machine seems to be utilizing /dev/crypto. > Typically I

Re: /dev/crypto not being used in 12-STABLE

2018-12-06 Thread Herbert J. Skuhra
On Thu, 06 Dec 2018 20:19:44 +0100, John Nielsen wrote: > > I have upgraded two physical machines from 11-STABLE to 12-STABLE > recently (one is 12.0-PRERELEASE r341380 and the other is > 12.0-PRERELEASE r341391). I noticed today that neither machine seems > to be utilizing /dev/crypto. Typically

/dev/crypto not being used in 12-STABLE

2018-12-06 Thread John Nielsen
I have upgraded two physical machines from 11-STABLE to 12-STABLE recently (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I noticed today that neither machine seems to be utilizing /dev/crypto. Typically I see at least ssh/sshd have the device open plus some programs