Custom Query (16 matches)
Results (4 - 6 of 16)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9 | fixed | Support GnuTLS version 3.0 | ||
| Description |
imported from mantis, dash reports: mod_gnutls should support the new ciphers in GnuTLS 3.0 |
|||
| #10 | fixed | Wildcards In ServerAlias Directive | ||
| Description |
imported from mantis, dash says:
Wildcards In Removing the wildcard on *.domain.tld, but leaving with *.sub.domain.tld works as expected and yields the desired page. E.G. One VHost domain.tld and one for sub.domain.tld aliased also as *.sub.domain.tld seems to work. What still doesn't is also aliasing the domain.tld as *.domain.tld |
|||
| #14 | fixed | Allow for configuration of parameters globally | ||
| Description |
imported from mantis, benbe wrote: It'd be nice if you could configure some parts like Cipher Priority, Certificate Chain File (yeah, that one makes sense), maybe even default Certificate (if you've got a wildcard which can be used as fallback), GnuTLS-based Auth Params, ... in the global Apache Configuration and get those values as a default if they aren't present in the actual VHost configuration. Additional Information Take this sample configuration: GnuTLSCertChain /etc/ssl/all_my_certs_chain.pem GnuTLSCipherPriority NONE:!MD5:!ANON-DH:!SSLv3:!SECURE128:+CIPHER-ALL:+TLS-ALL:... NameVirtualHost 1.1.1.1:80 <VirtualHost 1.1.1.1:80> ServerName foo.com GnuTLS on GnuTLSKeyFile /etc/ssl/mycert1.key GnuTLSCertFile /etc/ssl/mycert1.pem </VirtualHost> <VirtualHost 1.1.1.1:80> ServerName bar.com GnuTLS on GnuTLSKeyFile /etc/ssl/mycert2.key GnuTLSCertFile /etc/ssl/mycert2.pem </VirtualHost> Both VHosts should now be using the set priority string and send /etc/ssl/all_my_certs_chain.pem as their key chain (plus their actual certificate as the leaf). |
|||
