Jeremy Rowley (@GreatAmus) profile picture

Product dude at DigiCert. These tweets are my own opinion and not the views of my employer. They also aren't very good tweets...unless you like PKI memes.

Joined April 2014
Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)Photo by Jeremy Rowley (@GreatAmus)
Google announced its plan for CT log 2. It's a good plan. groups.google.com/a/chromium…
3
6
The validity period requirement only applies to leaf TLS server certs. support.apple.com/en-us/HT21…
2
4
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.
1
1
6
When Google announces it is removing the org name from the browser URL and were hoping for the green bar instead.
1
1
5
Maybe a stretch, but I wanted to put the info out there, and I laughed at the GIF for a long time.
1
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
Being a CA and watching all these new browser policies announced. Especially the changes to sMIME
1
1
3
I should have said "Especially when Mozilla clarifies that their policy prohibits delegation of email validation in SMIME"
1
1
3
Apple announcing no more support for private certs longer than 825 days and SHA1 certs
1
1
1
16
Clarification: This applies to all certs, regardless of EKU. You can override trust for individual certs that are longer than 825 days, but not SHA1
2
1
4
CAB Forum update 2: Me trying to slip identity updates past Ryan while he's looking elsewhere.
1
1
21
CAB Forum summary so far: 1) It's good to see everyone 2) The Network Security group is still working on stuff 3) Reorganizing document structure will save us all
1
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
1
30
1
56
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.
1
3
8
Jeremy Rowley retweeted
Some fixes, some news, some announcements. Read my #digicert #partner blog to get the latest updates! digicert.com/blog/countdown-…
1
2
1
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
The most interesting thing about this is the scope isn't limited to certs. If the CAB forum voted to write policy about how awful I smell after theoretically exercising, they could
2
5.3.1 allows groups consisting of issuers, consumers, or a combination of both.
1
1