-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
KeyFormat.SSH_RSA has Algorithm.SSH_RSA as the first candidate for algorithm, but it is not supported by node-http-signature:
| Arrays.asList(Algorithm.SSH_RSA, Algorithm.RSA_SHA1, Algorithm.RSA_SHA256, Algorithm.RSA_SHA512) |
For this to work without algorithms rotations, i do the following after a signer creation:
Collection<Algorithm> algorithms = Collections.singletonList(Algorithm.RSA_SHA256);
Challenge challenge = new Challenge("<preemptive>", Constants.DEFAULT_HEADERS, algorithms);
signer.rotateKeys(challenge);
Is this how it is supposed to be used? Can't there be more "out of the box experience" for this?
Why SSHKey here must have public key?
| if (keyPair.getPublic() == null) { |
It seems that presence of methods like canVerify and checks in verify method itself should prevent invalid use. Just curious. Use case is that a key used only for signing, not verifying.
Metadata
Metadata
Assignees
Labels
No labels