File

certs/localhost.cnf @ 13867:eabd38507c1d 13.0

util.jsonschema: Fix handling of `false` as schema Schemas can be either a boolean or a table (object) but since it only checked for truthiness, the case of `false` would be handled incorrectly. There seems to be no tests that cover `then` and `else` being `false`, only a couple that check the `if` keyword.
author Kim Alvefur <zash@zash.se>
date Sun, 30 Mar 2025 17:27:23 +0200
parent 7693:93c041d5bb0b
line wrap: on
line source

[v3_extensions]
basicConstraints = CA:TRUE
subjectAltName = @subject_alternative_name

[subject_alternative_name]
DNS.0 = localhost
otherName.0 = 1.3.6.1.5.5.7.8.7;IA5STRING:_xmpp-client.localhost
otherName.1 = 1.3.6.1.5.5.7.8.7;IA5STRING:_xmpp-server.localhost
otherName.2 = 1.3.6.1.5.5.7.8.5;FORMAT:UTF8,UTF8:localhost

[distinguished_name]
countryName = GB
organizationName = Prosody IM
organizationalUnitName = https://prosody.im/doc/certificates
commonName = Example certificate

[req]
prompt = no
x509_extensions = v3_extensions
req_extensions = v3_extensions
distinguished_name = distinguished_name