boring2/openssl/test
Steven Fackler 194298a057 Implement new feature setup
The basic idea here is that there is a feature for each supported
OpenSSL version. Enabling multiple features represents support for
multiple OpenSSL versions, but it's then up to you to check which
version you link against (probably by depending on openssl-sys and
making a build script similar to what openssl does).
2016-10-17 21:57:54 -07:00
..
alt_name_cert.pem Add accessors for x509 subject alt names 2016-04-29 21:15:32 -07:00
build.sh Add support for OpenSSL 1.1.0 2016-10-12 22:49:55 -07:00
cert.pem Start on PKCS #12 support 2016-08-14 10:11:38 -07:00
dhparams.pem Add DH::from_pem() to load DH parameters from a file 2015-09-13 12:44:50 +02:00
dsa-encrypted.pem add low level dsa primitives 2016-07-29 19:04:37 -04:00
dsa.pem add low level dsa primitives 2016-07-29 19:04:37 -04:00
dsa.pem.pub add low level dsa primitives 2016-07-29 19:04:37 -04:00
dsaparam.pem add low level dsa primitives 2016-07-29 19:04:37 -04:00
identity.p12 Start on PKCS #12 support 2016-08-14 10:11:38 -07:00
key.pem Update cert 2016-05-15 22:11:10 -07:00
key.pem.pub Add public key PEM read function. 2015-10-01 20:33:12 -04:00
nid_test_cert.pem Add a test that checks whether 3 known subject attributes can be retrieved by NID 2015-06-30 23:51:54 -07:00
nid_uid_test_cert.pem Fix Nid::UID value 2016-02-02 09:25:52 -08:00
root-ca.key Start on PKCS #12 support 2016-08-14 10:11:38 -07:00
root-ca.pem Start on PKCS #12 support 2016-08-14 10:11:38 -07:00
rsa-encrypted.pem Add an RSA key decryption test 2016-06-26 18:25:54 +02:00
rsa.pem add rsa signature tests 2016-05-05 23:41:55 +01:00
rsa.pem.pub add rsa signature tests 2016-05-05 23:41:55 +01:00
run.sh Implement new feature setup 2016-10-17 21:57:54 -07:00