Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Dec 2018 17:09:28 -0500
From:      Jung-uk Kim <jkim@FreeBSD.org>
To:        Jeremy Chadwick <jdc@koitsu.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: /dev/crypto not being used in 12-STABLE
Message-ID:  <5aa99bb2-09c8-5868-4302-6f5cd9fb4ea7@FreeBSD.org>
In-Reply-To: <8c7be0a2-65a7-2313-4c18-fab8ca89884a@FreeBSD.org>
References:  <20181207020124.GA87799@icarus.home.lan> <995cddb8-f4ce-b9c9-aa8f-5e7cd5c465e2@FreeBSD.org> <20181208003148.GA9469@icarus.home.lan> <8c7be0a2-65a7-2313-4c18-fab8ca89884a@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--n03TERMXwRuiDW8gEDEBIr1KgXSqaNgaS
Content-Type: multipart/mixed; boundary="R0snfOjDOduBDrczsrKAuxn2DkoFxXQYq";
 protected-headers="v1"
From: Jung-uk Kim <jkim@FreeBSD.org>
To: Jeremy Chadwick <jdc@koitsu.org>
Cc: freebsd-stable@freebsd.org
Message-ID: <5aa99bb2-09c8-5868-4302-6f5cd9fb4ea7@FreeBSD.org>
Subject: Re: /dev/crypto not being used in 12-STABLE
References: <20181207020124.GA87799@icarus.home.lan>
 <995cddb8-f4ce-b9c9-aa8f-5e7cd5c465e2@FreeBSD.org>
 <20181208003148.GA9469@icarus.home.lan>
 <8c7be0a2-65a7-2313-4c18-fab8ca89884a@FreeBSD.org>
In-Reply-To: <8c7be0a2-65a7-2313-4c18-fab8ca89884a@FreeBSD.org>

--R0snfOjDOduBDrczsrKAuxn2DkoFxXQYq
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 18. 12. 7., Jung-uk Kim wrote:
> On 18. 12. 7., Jeremy Chadwick wrote:
>> https://github.com/openssl/openssl/pull/3744/files#diff-e4eb329834da3d=
36278b1b7d943b3bc9
>>
>>   *) Add devcrypto engine.  This has been implemented against cryptode=
v-linux,
>>      then adjusted to work on FreeBSD 8.4 as well.
>>      Enable by configuring with 'enable-devcryptoeng'.  This is done b=
y default
>>      on BSD implementations, as cryptodev.h is assumed to exist on all=
 of them.
>>      [Richard Levitte]
>>
>> Is this message incorrect/false?
>=20
> Yes, it is incorrect.

It turned out to be a bug in the Configure script.  Now it is enabled by
default on head (r342009).  Please see the commit log for more info.

https://svnweb.freebsd.org/changeset/base/342009

Jung-uk Kim


--R0snfOjDOduBDrczsrKAuxn2DkoFxXQYq--

--n03TERMXwRuiDW8gEDEBIr1KgXSqaNgaS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlwRhx8ACgkQfJ+WJvzb
8UbDcQf6A/6bQ+jK6BMS8VNxrTIq9THw2LoptlTuIsOCvDQ49zc5t9QR6lGCxs1X
yPNliMO6x0sObc/wlG4hVphV8WUAvvDVSnjNj7x/q8qpIkZUs3CqxQFyx+FrEViq
BJ0crrpkjyeL5BdOBykmWGzkwG4fWAF5U+1SRXu2Kah6h05Pw9PpoScCM5vhu1Nc
87W0KTpaWEVdv0tUuZbEGnd/tPWt3uZoH1cYLuBkAg3hTnkhJOysijIbjHwST8pi
3JSY6PAFS2hF/unVs03Cqxts2U8bW8PQqqyPIwLsSDttD4y1lUY5jCGnkFbi24a8
Tit49lBFOchhkl0A/TWpZc+TfmsHDw==
=zO7m
-----END PGP SIGNATURE-----

--n03TERMXwRuiDW8gEDEBIr1KgXSqaNgaS--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5aa99bb2-09c8-5868-4302-6f5cd9fb4ea7>