3 ms·
The X.509 structure does put all of this together, it's just that cryptographers will tend to refer to the actual numbers which vary from one to another as the
by tialaramex 7y ago
The X.509 structure does put all of this together, it's just that cryptographers will tend to refer to the actual numbers which vary from one to another as the "public key" as a shorthand, they know the rest of the context is important but it's not what they're talking about right now.
In RSA for example there's a public exponent, yours is almost invariably going to be 65537 and most of the time nobody will even mention this parameter, but the "same" key with exponent 3 would actually be a different key than yours.
In code such shorthand becomes a bug.
If you only allow a handful of named algorithms the bug is essentially useless to adversaries. Microsoft's non-standard decision to allow parametrised curves makes it into a huge attack surface.
- sroussey 7y agoYeah, I get that! There would still be a named curve though, and things do change over time. Sometimes I like to force things in such a way that you can’t avoid dealing with some issues. So, by putting these items in the public key, you are forced to look at them and deal with them when you write a library. Often, engineers will write code correctly because they know all the context. But the next engineer will likely have less and less context as time goes by. Thus forcing context acknowledgement, while seemingly redundant, might be essential to avoiding future bugs.