3 ms·
One thing that'd be good here for outside observers is for Let's Encrypt to bake a list of the Blessed Methods used into certificates as OIDs in the Policy sect
by tialaramex 9y ago
One thing that'd be good here for outside observers is for Let's Encrypt to bake a list of the Blessed Methods used into certificates as OIDs in the Policy section.
Right now a researcher with 5 million Let's Encrypt certificates can see which ones use public keys with unusual patterns, how many are for names in the French .fr TLD, how many have longer key lengths, and so on, but they can't see whether the validation was done with Method 10 (which had this unexpected flaw) or some other method.
Another CA (can't remember which one) was looking at doing this, and it seems like it'd be nice for Let's Encrypt too.
- schoen 9y agoI like this kind of thing in principle, but certificates are already getting kind of large and there are a number of other things that one might put in them via OIDs. But I realize ASN.1 is pretty concise; do you know about how much this proposal would increase the size of a certificate by? Another concern might be that users might not want this to be disclosed because it might give attackers suggestions about how to attack their renewal processes (although of course CAs have been willing to publish information, like issued certs, that some users wouldn't prefer to make public).