Subject: CAcert Code Development list.
List archive
- From: Benny Baumann <benbe AT cacert.org>
- To: cacert-support AT lists.cacert.org
- Cc: Developers CAcert <cacert-devel AT lists.cacert.org>
- Subject: Re: Discrepances on the test server
- Date: Wed, 17 Feb 2016 15:59:46 +0100
Hi,
as there were some questions due to my earlier mail, just a short remark:
Am 16.02.2016 um 14:45 schrieb Benny Baumann:
> Am 16.02.2016 um 14:26 schrieb Ales Kastner:
>> There are 2 (two) different root (class 1) certs? One with the fingerprint
>> starting 2d3a31... (serial 0f), and the other with the fingerprint starting
>> 5b26e7... (serial 00). Or is the former the new one?
> The certificate with serial 0f is the one, that has been re-signed. Due
> to some incompatibilities found since the FrOSCon run an updated version
> compared to the resulting file from back then is currently installed.
After the re-signed test server root had been created at FrOSCon it has
been subject to various compatibility tests. One of those tests surfaced
an issue in different browsers that lead to rejection of the re-signed
root (e.g. in Firefox) if the serial number of the certificate was kept
equal. Discussing those incompatibilities with the Critical Admin Team
and other involved parties lead to the modified certificate with serial 0F.
The fingerprints on the test server root page will updated alongside
those of the re-signed production root.
Kind regards,
BenBE.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
- Re: Discrepances on the test server, Benny Baumann, 02/16/2016
- Re: Discrepances on the test server, Benny Baumann, 02/17/2016
Archive powered by MHonArc 2.6.18.