mod_posix: Move everything to util.startup This allows greater control over the order of events. Notably, the internal ordering between daemonization, initialization of libunbound and setup of signal handling is sensitive. libunbound starts a separate thread for processing DNS requests. If this thread is started before signal handling has been set up, it will not inherit the signal handlers and instead behave as it would have before signal handlers were set up, i.e. cause the whole process to immediately exit. libunbound is usually initialized on the first DNS request, usually triggered by an outgoing s2s connection attempt. If daemonization happens before signals have been set up, signals may not be processed at all.

     1

[v3_extensions]

     2

basicConstraints = CA:TRUE

     3

subjectAltName = @subject_alternative_name

     4

     5

[subject_alternative_name]

     6

DNS.0 = localhost

     7

otherName.0 = 1.3.6.1.5.5.7.8.7;IA5STRING:_xmpp-client.localhost

     8

otherName.1 = 1.3.6.1.5.5.7.8.7;IA5STRING:_xmpp-server.localhost

     9

otherName.2 = 1.3.6.1.5.5.7.8.5;FORMAT:UTF8,UTF8:localhost

    10

    11

[distinguished_name]

    12

countryName = GB

    13

organizationName = Prosody IM

    14

organizationalUnitName = https://prosody.im/doc/certificates

    15

commonName = Example certificate

    16

    17

[req]

    18

prompt = no

    19

x509_extensions = v3_extensions

    20

req_extensions = v3_extensions

    21

distinguished_name = distinguished_name

    22