Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RSA 186-5 KeyGen Failures #1465

Closed
bfussell opened this issue Aug 27, 2023 · 4 comments
Closed

RSA 186-5 KeyGen Failures #1465

bfussell opened this issue Aug 27, 2023 · 4 comments
Assignees
Milestone

Comments

@bfussell
Copy link
Collaborator

General question on RSA 186-5 key generation. I've run key gen using the following registration and my results match those retrieved from the sample request, however I get errors, included below(vsId included). What does "Internal key is unexpected type" indicate is wrong ?

Registration:
[{"acvVersion":"1.0"},{"isSample":true,"algorithms":[{"algorithm":"RSA","revision":"FIPS186-5","mode":"keyGen","prereqVals":[{"algorithm":"SHA","valValue":"same"},{"algorithm":"DRBG","valValue":"same"}],"infoGeneratedByServer":true,"pubExpMode":"random","keyFormat":"standard","capabilities":[{"randPQ":"probableWithProbableAux","properties":[{"modulo":2048,"pMod8":0,"qmod8":0,"hashAlg":[],"primeTest":["2pow100"]}]}]}]}]

Errors from server:
[
{
"acvVersion": "1.0"
},
{
"vsId": 1795266,
"disposition": "failed",
"tests": [
{
"tcId": 1,
"result": "failed",
"reason": "Internal key is unexpected type"
},
{
"tcId": 2,
"result": "failed",
"reason": "Internal key is unexpected type"
},
{
"tcId": 3,
"result": "failed",
"reason": "Internal key is unexpected type"
}
]
}
]

@jbrock24 jbrock24 self-assigned this Aug 28, 2023
@jbrock24
Copy link
Collaborator

jbrock24 commented Aug 29, 2023

Hi @bfussell, it turns out this is a bug that I'll be fixing. The error is stating that the internal read in key it's comparing to is not, in this case, of type standard and instead is CRT. The fix of this should go out in the next update. We'll reply here when it's released, thanks for letting us know!

@bfussell
Copy link
Collaborator Author

Great, thanks !

@livebe01 livebe01 added this to the v1.1.0.31 milestone Sep 19, 2023
@livebe01
Copy link
Collaborator

The fix for this is on Demo in release v1.1.0.31.

@livebe01
Copy link
Collaborator

The fix for this is on Prod in release v1.1.0.31.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants