Izenpe CT log operator inclusion request
Reported by inigo.ba...@gmail.com, May 24 2016
<b>Chrome Version : <Copy from: 'about:version'></b> Contact information: - email: firstname.lastname@example.org - Phone: +34-945067705 - contact persons: Iñigo Barreira and David Fernández endpoint: ct.izenpe.eus Base64 Log ID:iUFEnHB0Lga5/JznsRa6ACSqNtWa9E8CBEBPAPfqhWY= Operator: Izenpe HTTPS supported: yes Contact: email@example.com Maximum Merge Delay: 24 hours Description: Currently, the only policy in place is that the certificate is chained to a publicly trusted root certificate. However, during the testing and log inclusion process, we are only including the Izenpe trusted root and the google one as authorized. Additional root entries will be evaluated after receiving an inclusion request. We will likely develop our policies further based on the results from the discussions in the Trans working group and our own internal policies. Such policies may include an enforcement of BR and EV standards, a requirement for at least organizational vetting on the certificate, minimum key sizes and hash algorithms, and similar checks. Attached is the PEM file with the list of CAs included and the public key Regards
May 24 2016,
May 24 2016,
May 25 2016,
I've started monitoring the log yesterday - Should no issues be detected, the initial compliance monitoring phase will be complete on August 22nd. By the way, would you like to give the log an informal name? Right now I've got it down as "Izenpe 2nd log", but you can name it if you'd like :)
May 27 2016,
I prefer "new Izenpe log", to distinguish it from the old one.
Jun 7 2016,
Jun 20 2016,
Aug 25 2016,
Sorry to be the bearer of bad news, but as of the end of Argi's compliance monitoring period the observed availability of 93% is falling short of the required 99%. Once you've figured out & addressed whatever's causing the issue please do feel free to stand up a new log (on a new URL & with a new key) and re-apply with a fresh bug.
Oct 21 2016,
Sign in to add a comment