What platforms you were running our software when the bug happened ?
Linux
What happened ?
The problem is that cryptography keys don't use the same signature.
For example, we use RSA for sequester and ED25519 for internal, so we can maybe have others...
In our case, we sign the SequesterServiceCertificates with the SequesterAuthority's RSA key and others are signed with the root_signing_key, so we can't load with the same key.
Another problem is that RSA' signature depends on the key size (which is external of Parsec).
See the following snippet: The unsecure_unwrap of SequesterVerifyKeyDer should be implemented like this.
Version
2.16.0
What platforms you were running our software when the bug happened ?
Linux
What happened ?
The problem is that cryptography keys don't use the same signature. For example, we use
RSA
for sequester andED25519
for internal, so we can maybe have others...In our case, we sign the
SequesterServiceCertificates
with theSequesterAuthority
'sRSA
key and others are signed with theroot_signing_key
, so we can't load with the same key.Another problem is that
RSA
' signature depends on the key size (which is external ofParsec
).See the following snippet: The
unsecure_unwrap
ofSequesterVerifyKeyDer
should be implemented like this.Hence
AnyCertificate::unsecure_load
is invalid See this PR: https://github.com/Scille/parsec-cloud/pull/5387 which mentions the problem.Relevant output
No response