-
Notifications
You must be signed in to change notification settings - Fork 61
fix keymanager: use ed25519 for to sign manifest #1608
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine, but can we have a unit test that exercises this for both key algorithms?
Yes sure, but it still not clear for me how the different methods are processed on the BE, so far we have only one definition for the RSA algorithm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps it makes sense to add some low-level test(s) verifying if a signature method is set to an expected value and a signature actually matches the specified method (e.g. signature["method"] is set to rsassa-pss while it was actually signed by different method)
3f88cd0
to
595a6ac
Compare
Codecov Report
@@ Coverage Diff @@
## master #1608 +/- ##
==========================================
+ Coverage 82.68% 82.69% +0.01%
==========================================
Files 190 190
Lines 12079 12087 +8
==========================================
+ Hits 9987 9995 +8
Misses 2092 2092
Continue to review full report at Codecov.
|
Signed-off-by: Kostiantyn Bushko <kbushko@intellias.com>
Signed-off-by: Kostiantyn Bushko <kbushko@intellias.com>
09652f8
to
fe1fec5
Compare
This looks fine. How does the BE react to the manifest? |
Without this fix, the server response with the following error
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks!
Signed-off-by: Kostiantyn Bushko kbushko@intellias.com