Use different key to do OAEP and PSS #58
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I know it was a bad practice to use the same keypair to encrypt/decrypt and sign/verify...
secretin-lib/src/User.js
Lines 158 to 179 in 85873da
I used a "hack":
convertOAEPToPSS
And this is something ANSSI reported to me.
This PR solves the problem by generating another keypair dedicated to the signature process.
The
privateKeySign
is encrypted with a randomprotectKey
which is encrypted with the "normal"publicKey
.