Closed acartapanis closed 4 years ago
Hi, may I know why the previous comment was deleted ?
The solution proposed in the comment is working, but because of deletion of the previous comment, we rollbacked to cloudhsm-3.0.1-1 rather than using the proposed solution.
Are we supposed to open a case on aws support for this issue ?
Facing the same issue after the upgrade, what was the work around that worked for you?
Thank you for surfacing this issue. We are able to reproduce this issue and are working on a resolution.
This issue has been addressed with software version 3.1.1.
You can find the links to package and release notes here: https://docs.aws.amazon.com/cloudhsm/latest/userguide/client-history.html#client-version-3-1-1
Marking this issues as resolved.
After updating to 3.1.0, we have an error while loading a key by key handle.
The exception is :
The CaviumUtils.getKeyByHandle is an exact copy of https://github.com/aws-samples/aws-cloudhsm-jce-examples/blob/master/src/main/java/com/amazonaws/cloudhsm/examples/KeyUtilitiesRunner.java#L230
After some investigation, we find something strange in the CaviumKeyAttributes.getModulus method (CaviumKeyAttributes.java:106), specially when we compare it with the CloudHsmKeyAttributesMap.calculateModulus method (CloudHsmKeyAttributesMap.java:118).