Google announced its plan for CT log 2. It's a good plan. groups.google.com/a/chromium…
Jeremy Rowley retweeted
Replying to @matthegap @GreatAmus
The validity period requirement only applies to leaf TLS server certs. support.apple.com/en-us/HT21…
Jeremy Rowley retweeted
Replying to @GreatAmus
No it doesn't. It only applies to certs used for TLS Server auth. I'd love to burn it all down, but I can't. Users can override SHA-1 failures as well.
When Google announces it is removing the org name from the browser URL and were hoping for the green bar instead.
TBH, most of these 'changes' were predictable. I feel it's more like this for people who ignored the warning signs. For example, it was already in the Mozilla policy to verify domains. Google has already said they want shorter lived certs. And everyone wants to get rid of SHA1
2
5
I was watching Titans and was bothered that:
1) No one locks their computer ever. Billion dollar security but no locked computer policy. Maybe too realistic,
2) No one actually ages in 15 years. What is your secret Gotham?!
1
7
Jeremy Rowley retweeted
RFC 8410 is published!
It describes how to create x.509 certificates using curve25519 and curve448
tools.ietf.org/html/rfc8410
Not mine, but I thought it was funny. Ballot 219 clarified that following the CAA RFC was the right way to check CAA records. Basically, you can't issue a cert if the CAA record doesn't specify you a s the CA.
Jeremy Rowley retweeted
Some fixes, some news, some announcements. Read my #digicert #partner blog to get the latest updates!
digicert.com/blog/countdown-…
Nothing causes anxiety like traveling in Europe without a chip and pin card. Whether I can pay for something good is a roll of the dice.
2
Apparently (1.1 of the bylaws) the scope is to voluntary gather cert issuers and cert consumers. That leaves little guidance on what WGs should be created and not be created.
2
2



![[0xC001] (@ECCTLS) profile picture](https://pbs.twimg.com/profile_images/447594728997912576/VfwJWVzX_400x400.jpeg)


