That was what I was going to suggest when I kind of woke up this
morning: Find Russ and ask him...
On 3/19/24 03:37, Orie Steele wrote:
From Mike O.:
I asked Russ about the history of the duplicate signatureAlgorithm in
X.509.
The answer is that in like 1984 -- before PKCS#1 was invented, before
hash-then-sign was invented -- there was concern that some future
algorithms might sign by encrypting the TBSCertificate, and so you
would need to know the signatureAlgorithm in order to decrypt the
TBSCertificate. So the unprotected copy was put there literally as a
hint for how to parse the signature value in cases where the contents
of the TBSCertificate.signatureAlg is opaque.
So, yeah, it's 100% an artifact of evolution. Please get rid of it in
C509.
--
ORIE STEELEChief Technology Officerwww.transmute.industries
<https://transmute.industries>
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
