summaryrefslogtreecommitdiff
path: root/tests/crypto
AgeCommit message (Collapse)Author
2023-05-13openssl: More tests need -Wno-missing-field-initializers.riastradh
2023-05-13openssl: libcrypto bf test needs -Wno-missing-field-initializersriastradh
2023-05-11aarch64 needs staticchristos
2023-05-08make tests support both 1.x and 3.x.christos
Lot of work needed to add all the 3.x tests, but that can wait until all is switched
2022-06-10PR 56875: Bump timeout for the bignumber test to 2h, as suggestedmartin
by Tom Lane to give slower architectures a chance to complete it.
2022-05-21tests/crypto/opencrypto: Wait a bit for async results.riastradh
These may not be ready immediately.
2022-05-21opencrypto/h_ioctl: Print error messages with warn.riastradh
Might help track down what's going on when this fails.
2021-12-05s/rouine/routine/msaitoh
2020-04-11Double the timeout for the bn test case; 360 seconds is no longergson
sufficient under qemu since the latest openssl update.
2019-12-03Add HMAC-SHA-{256,384,512} test cases.hikaru
2019-06-16The runtime of the ecdsa test case increased approximately sixfoldgson
with the openssl update on 2019-06-09, and it is now timing out on sparc. Increase the timeout by roughly the same factor.
2019-03-27Timeout for evp test case is still not enough for qemu/sparcgson
2018-09-29A timeout of 480 seconds is not enough for the t_pubkey:ec test casegson
on qemu/sparc.
2018-09-29The default timeout of 300 seconds is not enough for the t_ciphers:evpgson
test case on qemu/sparc since the import of openssl 1.1.0i on 2018-08-18.
2018-09-28Force libcrypto to be loaded after libcryptotest for the benefit of sun2christos
2018-09-24Remove tests that don't exist anymore in OpenSSL-1.1.1 (We should add thechristos
one ones it adds though :-)
2018-09-23Merge openssl-1.1.1christos
2018-02-22PR lib/53044: remove tests not provided by OpenSSL 1.1.xmartin
2018-02-09put .PATH after the variable is defined.christos
2018-02-08fix 1.0 build; thanks ODE make.christos
2018-02-08include the right test directory for the right openssl versionchristos
2018-02-08adjust tests for 1.1christos
2017-06-14constify more to avoid gcc stupidity.christos
2017-06-13Avoid variable lenght buffers to help the stack protector (hopefully nomartin
functional change)
2017-06-09add tests of ioctl for /dev/cryptoknakahara
2017-05-21Remove MKCRYPTO option.riastradh
Originally, MKCRYPTO was introduced because the United States classified cryptography as a munition and restricted its export. The export controls were substantially relaxed fifteen years ago, and are essentially irrelevant for software with published source code. In the intervening time, nobody bothered to remove the option after its motivation -- the US export restriction -- was eliminated. I'm not aware of any other operating system that has a similar option; I expect it is mainly out of apathy for churn that we still have it. Today, cryptography is an essential part of modern computing -- you can't use the internet responsibly without cryptography. The position of the TNF board of directors is that TNF makes no representation that MKCRYPTO=no satisfies any country's cryptography regulations. My personal position is that the availability of cryptography is a basic human right; that any local laws restricting it to a privileged few are fundamentally immoral; and that it is wrong for developers to spend effort crippling cryptography to work around such laws. As proposed on tech-crypto, tech-security, and tech-userlevel to no objections: https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of *bad* crypto that was conditional on it, e.g. DES in telnet... That should probably be removed too, but on the grounds that it is bad, not on the grounds that it is (nominally) crypto.
2017-05-21Remove MKCRYPTO_RC5. Unconditionally include RC5 in libcrypto.so.riastradh
This option existed only because RC5 is covered by patents that, twenty years ago, we had reason to suspect the patent holder, RSA, Inc., might litigate. The two US patents in question are 5,724,428 and 5,835,600. According to the USPTO Patent Term Calculator web site at <https://www.uspto.gov/patent/laws-and-regulations/patent-term-calculator#heading-5> (retrieved 2017-05-21), patents filed after 1995-06-07 expire twenty years after the filing date. number filing date 5,724,428 1995-11-01 5,835,600 1997-04-21 Thus, these patents appear to be expired. As proposed on tech-crypto and tech-security: https://mail-index.netbsd.org/tech-crypto/2017/05/05/msg000718.html https://mail-index.netbsd.org/tech-security/2017/05/05/msg000927.html
2017-04-17add opencrypto atf for CRYPTO_3DES_CBC and ↵knakahara
CRYPTO_AES_CBC(=CRYPTO_RIJNDAEL128_CBC).
2016-10-14periphereal updates and generated files for the new openssl.spz
Expect at least one more commit until the tree builds again.
2016-10-13Bump timeouts so they work on a 32bit sparc (poor Krups)martin
2015-12-26For the skipped ARC4 test, don't bother trying to run the test clean-uppgoyette
code. It runs rump.halt which returns an error status (since rump was never started in the first place), and this causes atf to complain about the cleanup routine's return status, logging the test as a failure!
2015-03-16correct test nameprlw1
2014-01-19Sprinkle in some UNCONST()pgoyette
2014-01-18Include more of the test cases from RFC 1321.pgoyette
XXX cases 3, 6, and 9 are currently disabled because we don't seem to handle plain-text in other than 8-byte chunks.
2014-01-18Remove some debugging code.pgoyette
2014-01-18Free each crypto(4) session when we're done with it. (A new sessionpgoyette
is created for each test case.)
2014-01-18Fix verification to use correct buffer.pgoyette
Use test cases defined in RFC 1321
2014-01-18Add the test cases for sha1_hmacpgoyette
2014-01-18Needs some unconst.joerg
2014-01-17Additional tests for SHA1_HMAC (with test cases from RFC2202)pgoyette
2014-01-17Add additional test cases from RFC2202pgoyette
2014-01-17Use RFC 3713 vector, add comment to identify the sourcepgoyette
2014-01-17Reenable h_null (NULL_CBC) test. It works if we correctly pass a NULL iv.pgoyette
2014-01-17Clean up the helper programs. Remove the code to print the results, andpgoyette
make sure that all helpers actually check the results against the correct values.
2014-01-17Disable the arc4 and null_cbc tests for now. The swcrypto driver doespgoyette
not (yet) support them.
2014-01-16Use __arraycount and size_t as the format strings are wrong anyway.joerg
2014-01-16Since sizeof() is unsigned, use an unsigned int for the loop index.pgoyette
Fixes latest build break.
2014-01-16Include all of the examples from RFC3566pgoyette
2014-01-15Remove bogus TESTSDIRmartin
2014-01-14Descend into new opencrypto test suitepgoyette