a V1/V2 certificate must not have any V3 extensions
style
style: rename subject to subject_common_name
use subject common name as well as subject alternative name as hostnames of the cert
introduce version_matches_extensions (which assures that V1 and V2 do not contain extensions);
and use this function in is_cert_valid, is_ca_cert_valid, is_server_cert_valid
fix wildcard matching: foobar.com matches *.foobar.com
check that if a ca certificate has an extended key usage, this must be any
 (will be refined once we support OCSP)
style
allow ext_authority_matches_subject to pass if either certificate does not have the
requested extension
introduce new test module X509tests
move cs_mmap to Testlib
provide a X509 test suite and handcrafted sample certificates together with openssl.cnf
revert to require ext_key_usage to be either empty or any in CA cert
adjust to current certificate change
provide an intermediate CA without basicConstraint, which should fail
provide a server certificate without common name or subject alternative name, which should fail
remove signing request from repo
provide certificate with key usage critical ; and one with email in subjaltname
more tests for invalid chains, CAs (X509v1 intermediate CA, empty trust anchor, broken chains)
some valid and invalid chains
Merge pull request #115 from mirleft/x509-fixes

X509 fixes and testsuite