zeek/testing/btest/scripts/base/files/x509
Johanna Amann 833168090a Add ability to check if hostname is valid for a specific cert
This commit adds two new bifs, x509_check_hostname and
x509_check_cert_hostname. These bifs can be used to check if a given
hostname which can, e.g., be sent in a SNI is valid for a specific
certificate.

This PR furthermore modifies the ssl logs again, and adds information
about this to the log-file. Furthermore we now by default remove the
server certificate information from ssl.log - I doubt that this is often
looked at, it is not present in TLS 1.3, we do still have the SNI, and
if you need it you have the information in x509.log.

This also fixes a small potential problem in X509.cc assuming there
might be SAN-entries that contain null-bytes.

Baseline update will follow in another commit.
2021-06-29 15:00:48 +01:00
..
1999.test General btest cleanup 2020-08-11 11:26:22 -07:00
caching-hook.test General btest cleanup 2020-08-11 11:26:22 -07:00
disable-certificate-events-known-certs.zeek Add policy script suppressing certificate events 2021-06-29 11:39:18 +01:00
event-caching.test Implement X509 certificate log caching 2021-06-29 09:41:40 +01:00
files.test Change SSL and X.509 logging format 2021-06-29 09:26:43 +01:00
log-caching-cluster.test Implement X509 certificate log caching 2021-06-29 09:41:40 +01:00
log-caching-disabled-cluster.test Implement X509 certificate log caching 2021-06-29 09:41:40 +01:00
log-caching.test Implement X509 certificate log caching 2021-06-29 09:41:40 +01:00
signed_certificate_timestamp.test &is_set => &is_assigned 2021-02-04 12:18:46 -08:00
signed_certificate_timestamp_ocsp.test &is_set => &is_assigned 2021-02-04 12:18:46 -08:00
x509_check_cert_hostname.zeek Add ability to check if hostname is valid for a specific cert 2021-06-29 15:00:48 +01:00