[Savannah-help-public] [sr #106474] CN in TLS certificate (savannah.*gnu.org) is too broad -- use SubjectAltNames instead.

2008-09-13 Thread Sylvain Beucler
Follow-up Comment #3, sr #106474 (project administration): > though the current certificate doesn't properly indicate savannah.nongnu.org, as you know Hmmm, actually that's a mistake that I shamelessly didn't test -_-' Fixed now. I had decided to use 2 certs in a first step with CAcert. We hav

[Savannah-help-public] [sr #106474] CN in TLS certificate (savannah.*gnu.org) is too broad -- use SubjectAltNames instead.

2008-09-13 Thread Daniel Kahn Gillmor
Follow-up Comment #2, sr #106474 (project administration): Switching to CAcert probably is a good idea (though the current certificate doesn't properly indicate savannah.nongnu.org, as you know). I actually looked at certtool before submitting this ticket, and couldn't figure out how to get two

[Savannah-help-public] [sr #104690] cacert.org SSL Certificates

2008-09-13 Thread Sylvain Beucler
Update of sr #104690 (project administration): Status: Need Info => Done ___ Follow-up Comment #8: We installed certificates from cacert.org at savannah.gnu.org and savannah.nongnu.org. C

[Savannah-help-public] [sr #106474] CN in TLS certificate (savannah.*gnu.org) is too broad -- use SubjectAltNames instead.

2008-09-13 Thread Sylvain Beucler
Update of sr #106474 (project administration): Status:None => Done Assigned to:None => Beuc Open/Closed:Open => Closed __