aboutsummaryrefslogtreecommitdiff
path: root/tools/tools/crypto
Commit message (Collapse)AuthorAgeFilesLines
* cryptocheck: Add aliases for algs with multiple key sizes.John Baldwin2022-01-061-16/+44
| | | | | | | | | | | | | | | | | | | | Previously algorithms such as AES-CBC would provide an algorithm without a key size for the smallest key size and additional algorithms with an explicit key size, e.g. "aes-cbc" (128 bits), "aes-cbc192", and "aes-cbc256". Instead, always make the key size name explicit and reuse the "generic" name to request running tests against all of the key sizes. For example, for AES-CBC this means "aes-cbc128" is now the name of the variant with a 128-bit key and "aes-cbc" runs tests of AES-CBC with all three key sizes. This makes it easier to run tests on all combinations of ciphers like AES-GCM or AES-CCM with -z in a single invocation. Reviewed by: markj Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D33759
* OCF: Hook up plain RIPEMD160 in cryptosoft and /dev/crypto.John Baldwin2021-12-301-0/+2
| | | | | | Reviewed by: markj Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D33612
* cryptocheck: Test Camellia-CBC cipher and RIPEMD-160 HMAC.John Baldwin2021-12-161-0/+13
| | | | | | Reviewed by: markj Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D33518
* crypto: Support Chacha20-Poly1305 with a nonce size of 8 bytes.John Baldwin2021-10-061-2/+2
| | | | | | | | | | | | | | This is useful for WireGuard which uses a nonce of 8 bytes rather than the 12 bytes used for IPsec and TLS. Note that this also fixes a (should be) harmless bug in ossl(4) where the counter was incorrectly treated as a 64-bit counter instead of a 32-bit counter in terms of wrapping when using a 12 byte nonce. However, this required a single message (TLS record) longer than 64 * (2^32 - 1) bytes (about 256 GB) to trigger. Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D32122
* cryptocheck: Support multiple IV sizes for AES-CCM.John Baldwin2021-10-061-80/+156
| | | | | | | | | | By default, the "normal" IV size (12) is used, but it can be overriden via -I. If -I is not specified and -z is specified, issue requests for all possible IV sizes. Reviewed by: markj Sponsored by: Chelsio Communications, The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D32110
* OCF: Remove support for asymmetric cryptographic operations.John Baldwin2021-04-122-274/+1
| | | | | | | | | | | | There haven't been any non-obscure drivers that supported this functionality and it has been impossible to test to ensure that it still works. The only known consumer of this interface was the engine in OpenSSL < 1.1. Modern OpenSSL versions do not include support for this interface as it was not well-documented. Reviewed by: cem Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D29736
* cryptocheck: Expand the set of sizes tested by -z.John Baldwin2021-04-011-3/+9
| | | | | | | | | | Test individual sizes up to the max encryption block length as well as a few sizes that include 1 full block and a partial block before doubling the size. Reviewed by: cem, markj Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D29518
* cryptocheck: Free generated IV after each GMAC test.John Baldwin2021-03-031-0/+1
| | | | | | Reviewed by: cem Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D28753
* cryptocheck: Add support for the Poly1305 digest.John Baldwin2021-03-031-5/+85
| | | | | Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D28758
* cryptocheck: Add Chacha20-Poly1305 AEAD coverage.John Baldwin2021-02-181-19/+27
| | | | | | | | | | | - Make openssl_gcm_encrypt generic to AEAD ciphers (aside from CCM) and use it for Chacha20-Poly1305. - Use generic AEAD control constants instead of GCM/CCM specific names. Reviewed by: cem Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D27838
* Remove uses of CRIOGET in OCF tests after r368005.John Baldwin2020-11-252-18/+3
| | | | | | | | | Pointy hat to: jhb Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D27367 Notes: svn path=/head/; revision=368008
* Remove the cloned file descriptors for /dev/crypto.John Baldwin2020-11-251-17/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Crypto file descriptors were added in the original OCF import as a way to provide per-open data (specifically the list of symmetric sessions). However, this gives a bit of a confusing API where one has to open /dev/crypto and then invoke an ioctl to obtain a second file descriptor. This also does not match the API used with /dev/crypto on other BSDs or with Linux's /dev/crypto driver. Character devices have gained support for per-open data via cdevpriv since OCF was imported, so use cdevpriv to simplify the userland API by permitting ioctls directly on /dev/crypto descriptors. To provide backwards compatibility, CRIOGET now opens another /dev/crypto descriptor via kern_openat() rather than dup'ing the existing file descriptor. This preserves prior semantics in case CRIOGET is invoked multiple times on a single file descriptor. Reviewed by: markj Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D27302 Notes: svn path=/head/; revision=368005
* Remove unnecessary __DECONST().John Baldwin2020-11-031-19/+19
| | | | | | | | | Reviewed by: markj Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D27063 Notes: svn path=/head/; revision=367311
* Fix various warnings with higher WARNS.John Baldwin2020-10-131-59/+58
| | | | | | | | | - Rename global 'crid' to 'requested_crid' to avoid shadowing. - Remove some unused function arguments. - Use __DECONST(). Notes: svn path=/head/; revision=366687
* Expand coverage of different buffer sizes.John Baldwin2020-05-251-79/+156
| | | | | | | | | | | | | | | | | | | | | | | | | | - When -z is used, include small buffers from 1 to 32 bytes to test stream ciphers. Note that while AES-XTS claims to support a block size of 1 in OpenSSL, it does require a minimum of 1 block of cipher text as it is not a stream cipher but depends on CTS to pad out the final partial block. - Permit multiple AAD sizes to be set via multiple -A options, or via -z. When -z is set, use small buffers from 0 to 32 bytes followed by powers of 2 up to 256. When multiple sizes are specified, the ETA and AEAD algorithms perform the full matrix of AAD sizes by payload sizes. - Only warn on unchanged ciphertext instead of erroring. The currently generated plaintext and key for a couple of AES-CTR tests with a buffer size of 1 results in ciphertext that matches the plaintext. Reviewed by: cem Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D25006 Notes: svn path=/head/; revision=361487
* Remove the ubsecstats tool since ubsec(4) has been removed.John Baldwin2020-05-152-76/+1
| | | | | | | Reported by: markj Notes: svn path=/head/; revision=361091
* Refactor driver and consumer interfaces for OCF (in-kernel crypto).John Baldwin2020-03-271-32/+164
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677 Notes: svn path=/head/; revision=359374
* Various cleanups to cryptocheck.John Baldwin2020-01-071-450/+344
| | | | | | | | | | | | | | | | | | | | | - Rename 'blkcipher' to 'cipher'. Some of the ciphers being tested are stream ciphers. - Rename 'authenc' to 'eta' as it is only testing ETA chained operations and not other combination modes. - Add a notion of an OCF session and some helper routines to try to reduce duplicated code. This also uses a single session for both encrypt and decrypt operations during a single test. - Add tests to ensure that AEAD algorithms fail decryption with EBADMSG when given a corrupted tag. - Remove the transitional hack for COP_F_CIPHER_FIRST. - Update block comment to mention plain hashes. Reviewed by: cem Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D22940 Notes: svn path=/head/; revision=356457
* tools/tools/crypto: cryptokeytest: Fix build with newer OpenSSLConrad Meyer2019-08-091-61/+47
| | | | | | | Also, drag into this decade. Notes: svn path=/head/; revision=350813
* Have cryptocheck toggle kern.cryptodevallowsoft if necessary (thisSean Eric Fagan2019-02-271-1/+30
| | | | | | | | | | | requires root access). Reviewed by: cem, jhb Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D19372 Notes: svn path=/head/; revision=344630
* It turns out that setting the IV length is necessary with CCM in OpenSSL.Sean Eric Fagan2019-02-201-0/+3
| | | | | | | | | This adds that back. Reviewed by: cem Notes: svn path=/head/; revision=344388
* Add AES-CCM encryption, and plumb into OCF.Sean Eric Fagan2019-02-151-2/+226
| | | | | | | | | | | | | | | | | | | | | | This commit essentially has three parts: * Add the AES-CCM encryption hooks. This is in and of itself fairly small, as there is only a small difference between CCM and the other ICM-based algorithms. * Hook the code into the OpenCrypto framework. This is the bulk of the changes, as the algorithm type has to be checked for, and the differences between it and GCM dealt with. * Update the cryptocheck tool to be aware of it. This is invaluable for confirming that the code works. This is a software-only implementation, meaning that the performance is very low. Sponsored by: iXsystems Inc. Differential Revision: https://reviews.freebsd.org/D19090 Notes: svn path=/head/; revision=344141
* Compile cryptocheck with in-tree openssl again.John Baldwin2018-11-011-4/+1
| | | | | | | | | | Reviewed by: cem MFC after: 2 months Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D17767 Notes: svn path=/head/; revision=340018
* cryptocheck: Correct mismatch between OpenSSL use and OCF Blake2Conrad Meyer2018-07-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | This corrects a mistake introduced to the cryptocheck tool in r331418. Our CRYPTO_BLAKE2B and CRYPTO_BLAKE2S algorithms refer to either the plain, unkeyed hashes (specified with cri_klen = 0), or a Blake2-specific keyed MAC (when a cri_key is provided). In contrast, OpenSSL's Blake2 algorithms only provide the plain hash. Cryptocheck's T_HMAC corresponds to OpenSSL's HMAC() routine, which is the ordinary HMAC construction applied to any plain, unkeyed hash. We don't have any HMAC-Blake2 cipher modes in OCF, so fix the test to only test Blake2 as a plain hash. (Ideally we would test keyed Blake2 as well, but that is left as future work.) PR: 229795 Notes: svn path=/head/; revision=336527
* OCF: Add plain hash modesConrad Meyer2018-07-091-7/+155
| | | | | | | | | | | | | | | | | | | | | | | | | | | In part, to support OpenSSL's use of cryptodev, which puts the HMAC pieces in software and only offloads the raw hash primitive. The following cryptodev identifiers are added: * CRYPTO_RIPEMD160 (not hooked up) * CRYPTO_SHA2_224 * CRYPTO_SHA2_256 * CRYPTO_SHA2_384 * CRYPTO_SHA2_512 The plain SHA1 and 2 hashes are plumbed through cryptodev (feels like there is a lot of redundancy here...) and cryptosoft. This adds new auth_hash implementations for the plain hashes, as well as SHA1 (which had a cryptodev.h identifier, but no implementation). Add plain SHA 1 and 2 hash tests to the cryptocheck tool. Motivation stems from John Baldwin's earlier OCF email, https://lists.freebsd.org/pipermail/freebsd-arch/2018-January/018835.html . Notes: svn path=/head/; revision=336125
* OCF: Add CRYPTO_SHA2_224_HMAC modeConrad Meyer2018-07-091-0/+2
| | | | | | | | | Round out the complete set of basic SHA2 HMAC modes with SHA2-224. Support is added to the cryptocheck test tool. Notes: svn path=/head/; revision=336124
* Add a SPD cache to speed up lookups.Fabien Thomas2018-05-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | When large SPDs are used, we face two problems: - too many CPU cycles are spent during the linear searches in the SPD for each packet - too much contention on multi socket systems, since we use a single shared lock. Main changes: - added the sysctl tree 'net.key.spdcache' to control the SPD cache (disabled by default). - cache the sp indexes that are used to perform SP lookups. - use a range of dedicated mutexes to protect the cache lines. Submitted by: Emeric Poupon <emeric.poupon@stormshield.eu> Reviewed by: ae Sponsored by: Stormshield Differential Revision: https://reviews.freebsd.org/D15050 Notes: svn path=/head/; revision=334054
* cryptocheck: Add Chacha20 cipher to toolConrad Meyer2018-03-291-0/+3
| | | | Notes: svn path=/head/; revision=331726
* cryptotest: Add chacha20 cipherConrad Meyer2018-03-291-1/+3
| | | | Notes: svn path=/head/; revision=331725
* cryptotest: Add blake2 hashes to toolConrad Meyer2018-03-271-0/+5
| | | | | | | Sponsored by: Dell EMC Isilon Notes: svn path=/head/; revision=331628
* Update the license to note my work on cryptocheck was sponsored.John Baldwin2018-03-261-1/+26
| | | | | | | Sponsored by: Chelsio Communications Notes: svn path=/head/; revision=331597
* cryptocheck: Add support for Blake2{B,S} hashesConrad Meyer2018-03-232-1/+10
| | | | | | | | | | Since they are not yet present in the version of openssl in base, this will require installing the ports openssl. Sponsored by: Dell EMC Isilon Notes: svn path=/head/; revision=331418
* Bring in JHB's cryptocheck toolConrad Meyer2018-03-232-31/+1183
| | | | | | | | | | | | | | | | | It can be used to validate basic algorithm correctness on a variety of inputs, by comarison to openssl. While here, add some sanity to the crypto/Makefile. The tool may not be perfect, but getting it in tree where collaboration can happen is a nice first step. The pace of development outside of svn seems to have slowed down mid-2017. Obtained from: github bsdjhb/freebsd:cryptocheck Sponsored by: Dell EMC Isilon Notes: svn path=/head/; revision=331417
* Add encrypt+authenticate modes to cryptotest toolConrad Meyer2018-01-101-25/+60
| | | | | | | | | | | | | | | | | | | | Like jhb's cryptocheck (uncommitted so far), express encrypt+authenticate modes as "-a <encalg>+<authalg>". Example use with aesni(4) on AMD Zen family: $ ./cryptotest -d aesni0 -a aes256 10000 $((128*1024)) 2.331 sec, 20000 aes256 crypts, 131072 bytes, 1124707930 byte/sec, 8580.8 Mb/sec $ ./cryptotest -d aesni0 -a sha256 10000 $((128*1024)) 1.109 sec, 10000 sha256 crypts, 131072 bytes, 1181577161 byte/sec, 9014.7 Mb/sec $ ./cryptotest -d aesni0 -a aes256+sha256 10000 $((128*1024)) 3.805 sec, 10000 sha256+aes256 crypts, 131072 bytes, 344460116 byte/sec, 2628.0 Mb/sec Reported by: jhb Sponsored by: Dell EMC Isilon Notes: svn path=/head/; revision=327802
* Fix some new errors and a warning in cryptotest.John Baldwin2017-06-011-8/+10
| | | | | | | | | | | | | | | - Use a new 'char *key' to allocate storage for keys and assign the pointer to the session2_op 'const char *' members after the key is initialized. - Mark the 'find' variable used in crfind() static so that crfind() doesn't return a pointer to stack garbage. Reported by: olivier (1) MFC after: 2 weeks Sponsored by: Chelsio Communications Notes: svn path=/head/; revision=319475
* Add cpuset support to separate forked processes.George V. Neville-Neil2016-09-031-0/+9
| | | | | | | | | Reviewed by: cem Sponsored by: Rubicon Communications, LLC (Netgate) Differential Revision: https://reviews.freebsd.org/D7766 Notes: svn path=/head/; revision=305312
* Add a runner script for cryptotest.George V. Neville-Neil2016-09-021-0/+32
| | | | | | | | | | | | | | | Althought cryptotest itself has a -z mode to test all algorithms at a variety of sizes, this script allows us to be more selective. Threads and buffer sizes move in powers of two from 1, for threads, and 256 for buffer sizes. e.g. cryptorun.sh aes 4 512 Test aes with 1, 2 and 4 processes, and at sizes of 256 and 512 bytes. Sponsored by: Rubicon Communications, LLC (Netgate) Notes: svn path=/head/; revision=305307
* Clean up the usage message and remove dead code.George V. Neville-Neil2016-09-021-12/+4
| | | | | | | | | | Reviewed by: cem MFC after: 2 weeks Sponsored by: Rubicon Communications, LLC (Netgate) Differential Revision: https://reviews.freebsd.org/D7765 Notes: svn path=/head/; revision=305304
* Update cryptotest for modern algorithmsGeorge V. Neville-Neil2016-08-301-20/+25
| | | | | | | | | Reviewed by: cem Sponsored by: Rubicon Communications, LLC (Netgate) Differential Revision: https://reviews.freebsd.org/D7598 Notes: svn path=/head/; revision=305066
* - Replace N(a)/N(i)/N(T)/LEN(a)/ARRAY_SIZE(a) with nitems()Craig Rodrigues2015-08-296-31/+54
| | | | | | | | | | | - Add missing <err.h> for err() and <sys/sysctl.h> for sysctlbyname() - NULL -> 0 for 5th parameter of sysctlbyname() Submitted by: Andriy Voskoboinyk <s3erios@gmail com> Differential Revision: https://reviews.freebsd.org/D3442 Notes: svn path=/head/; revision=287297
* Include stdint.h to fix build.Andrey V. Elsukov2013-07-291-1/+2
| | | | | | | Pointed by: Olivier Cochard-Labbé Notes: svn path=/head/; revision=253767
* Prepare network statistics structures for migration to PCPU counters.Andrey V. Elsukov2013-07-091-28/+26
| | | | | | | | | | | | | Use uint64_t as type for all fields of structures. Changed structures: ahstat, arpstat, espstat, icmp6_ifstat, icmp6stat, in6_ifstat, ip6stat, ipcompstat, ipipstat, ipsecstat, mrt6stat, mrtstat, pfkeystat, pim6stat, pimstat, rip6stat, udpstat. Discussed with: arch@ Notes: svn path=/head/; revision=253081
* Increase cryptotest tool initialization vector (IV) size.Rafal Jaworowski2008-08-211-1/+1
| | | | | | | | | | | This fixes potential out-of-bound accesses when testing ciphers with block size greater than 8 bytes (e.g. AES). Submitted by: Bartlomiej Sieka tur ! semihalf dot com Discussed with: pjd, sam Notes: svn path=/head/; revision=181965
* Add missing includes and correct argument to sysctlbynameMatteo Riondato2008-02-052-1/+4
| | | | | | | | PR: misc/120274 MFC after: 1 week Notes: svn path=/head/; revision=175979
* Update structure name to follow the new IPsec code.George V. Neville-Neil2007-09-191-1/+1
| | | | | | | | Reported by: phk Approved by: re Notes: svn path=/head/; revision=172240
* Overhaul driver/subsystem api's:Sam Leffler2007-03-212-20/+122
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | o make all crypto drivers have a device_t; pseudo drivers like the s/w crypto driver synthesize one o change the api between the crypto subsystem and drivers to use kobj; cryptodev_if.m defines this api o use the fact that all crypto drivers now have a device_t to add support for specifying which of several potential devices to use when doing crypto operations o add new ioctls that allow user apps to select a specific crypto device to use (previous ioctls maintained for compatibility) o overhaul crypto subsystem code to eliminate lots of cruft and hide implementation details from drivers o bring in numerous fixes from Michale Richardson/hifn; mostly for 795x parts o add an optional mechanism for mmap'ing the hifn 795x public key h/w to user space for use by openssl (not enabled by default) o update crypto test tools to use new ioctl's and add cmd line options to specify a device to use for tests These changes will also enable much future work on improving the core crypto subsystem; including proper load balancing and interposing code between the core and drivers to dispatch small operations to the s/w driver as appropriate. These changes were instigated by the work of Michael Richardson. Reviewed by: pjd Approved by: re Notes: svn path=/head/; revision=167755
* make cryptotest compile after the latest changes to cryptodev.hMichael Reifenberger2006-05-241-3/+3
| | | | Notes: svn path=/head/; revision=158886
* Add missing stats.hst_nodesc statistics.Pawel Jakub Dawidek2006-05-181-2/+4
| | | | Notes: svn path=/head/; revision=158719
* ioctl(2) commands are u_long not int.Poul-Henning Kamp2005-01-181-5/+5
| | | | | | | Pass zero for sysctl new argument length, not NULL); Notes: svn path=/head/; revision=140407
* new version of cryptotest (w/ only code from me)Sam Leffler2004-09-072-1/+583
| | | | | | | Reviewed by: imp Notes: svn path=/head/; revision=134911
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 06:53:16 +0000