John Baldwin a3d565a118 Add a crypto capability flag for accelerated software drivers. ... Use this in GELI to print out a different message when accelerated software such as AESNI is used vs plain software crypto. While here, simplify the logic in GELI a bit for determing which type of crypto driver was chosen the first time by examining the capabilities of the matched driver after a single call to crypto_newsession rather than making separate calls with different flags. Reviewed by: delphij Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D25126		2020-06-09 22:26:07 +00:00
..
aesni	Add a crypto capability flag for accelerated software drivers.	2020-06-09 22:26:07 +00:00
armv8	Add a crypto capability flag for accelerated software drivers.	2020-06-09 22:26:07 +00:00
blake2	Add a crypto capability flag for accelerated software drivers.	2020-06-09 22:26:07 +00:00
camellia
ccp	Add support for optional separate output buffers to in-kernel crypto.	2020-05-25 22:12:04 +00:00
chacha20	Improve support for stream ciphers in the software encryption interface.	2020-05-22 16:29:09 +00:00
des	Stop using des_cblock * for arguments to DES functions.	2019-08-26 17:25:07 +00:00
libsodium	Bring in compatibility glue for libsodium	2018-08-17 00:27:56 +00:00
rc4
rijndael	rijndael (AES): Avoid leaking sensitive data on kernel stack	2018-10-26 20:53:01 +00:00
sha2	libmd: Always erase context in _Final method, and when doing	2018-07-20 07:01:28 +00:00
siphash
skein	Rename skein_block_asm.s to .S and assemble using Clang IAS	2020-06-06 00:35:41 +00:00
via	Add a crypto capability flag for accelerated software drivers.	2020-06-09 22:26:07 +00:00
intake.h
sha1.c
sha1.h