On Sat, January 16, 2016 22:15, Robert Edmonds wrote:
> Axel Beckert wrote:
>> So why was the CA then removed already if debconf.org still uses this
>> CA? https://www.debconf.org/ is now reported as broken.
>
> Hi,
>
> If you examine the certificate served by www.debconf.org:443, it has a
>
Axel Beckert wrote:
> So why was the CA then removed already if debconf.org still uses this
> CA? https://www.debconf.org/ is now reported as broken.
Hi,
If you examine the certificate served by www.debconf.org:443, it has a
common name of wiki.debconf.org, with SANs for wiki.debconf.org and
Raphael Geissert wrote:
> Just a bug report to track the removal of the SPI CA.
*sigh*
> As far as I'm aware of, only the debconf.org websites still use
> certificates signed by that CA.
So why was the CA then removed already if debconf.org still uses this
CA? https://www.debconf.org/ is now
Hi,
+1 on removal of this CA from the default system trusted CA
certificates. I get why back in the day CAcert and similar
projects looked like a valid idea, but the CA landscape has changed
significantly [0] since then and a CA that does not conform with
modern technical and operational
Package: ca-certificates
Version: 20150426
Severity: important
Just a bug report to track the removal of the SPI CA.
As far as I'm aware of, only the debconf.org websites still use
certificates signed by that CA.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
5 matches
Mail list logo
