Closed mbwang closed 3 years ago
Am Dienstag, dem 16.03.2021 um 16:19 -0700 schrieb mbwang:
Hi,
I'm testing out the KTS IFC implementation and received the following error with the following test case. I got the test case manually from ACVP server and tested on fedora 29's openssl.
Error message
ACVPParser (18:34:13) Error: RSA OAEP decryption failed error:04099079:rsa routines:RSA_padding_check_PKCS1_OAEP_mgf1:oaep decoding error ACVPParser (18:34:13) Error: Test execution failed ACVPParser( 18:34:13) Parsing processdata failed
I can confirm that I see that error with your test vector.
The test case looks a bit different than what I tested and which worked. I tried to re-test it but the server seems to be slow.
Here is the cipher request I send to the server
[
{
"acvVersion":"1.0"
},
{
"isSample":false,
"operation":"register",
"certificateRequest":"no",
"debugRequest":"yes",
"production":"no",
"encryptAtRest":"yes",
"algorithms":[
{
"prereqVals":[
{
"algorithm":"SHA",
"valValue":"same"
},
{
"algorithm":"DRBG",
"valValue":"same"
}
],
"algorithm":"KTS-IFC",
"revision":"Sp800-56Br2",
"function":[
"partialVal"
],
"iutId":"0123456789abcdef",
"keyGenerationMethods":[
"rsakpg1-basic"
],
"modulo":[
2048,
3072,
4096,
6144,
8192
],
"fixedPubExp":"010001",
"scheme":{
"KTS-OAEP-basic":{
"kasRole":[
"initiator",
"responder"
],
"ktsMethod":{
"hashAlgs":[
"SHA2-224",
"SHA2-256",
"SHA2-384",
"SHA2-512",
"SHA3-224",
"SHA3-256",
"SHA3-384",
"SHA3-512"
],
"supportsNullAssociatedData":true,
"fixedInfoPattern":"uPartyInfo||vPartyInfo",
"encoding":[
"concatenation"
]
},
"l":768
}
}
}
]
}
]
confirmed - with the request given above, it works
Thanks, that request worked for me too. The request I was using also had associatedDataPattern
, which I think is causing the issue. Here is the request:
[
{
"acvVersion":"1.0"
},
{
"isSample":false,
"operation":"register",
"certificateRequest":"no",
"debugRequest":"yes",
"production":"no",
"encryptAtRest":"yes",
"algorithms":[
{
"prereqVals":[
{
"algorithm":"SHA",
"valValue":"same"
},
{
"algorithm":"DRBG",
"valValue":"same"
}
],
"algorithm":"KTS-IFC",
"revision":"Sp800-56Br2",
"function":[
"partialVal"
],
"iutId":"0123456789abcdef",
"keyGenerationMethods":[
"rsakpg1-basic"
],
"modulo":[
2048
],
"fixedPubExp":"010001",
"scheme":{
"KTS-OAEP-basic":{
"kasRole":[
"initiator",
"responder"
],
"ktsMethod":{
"hashAlgs":[
"SHA2-224"
],
"supportsNullAssociatedData":true,
"associatedDataPattern":"uPartyInfo||vPartyInfo",
"encoding":[
"concatenation"
]
},
"l":768
}
}
}
]
}
]
Am Montag, dem 22.03.2021 um 14:51 -0700 schrieb mbwang:
Thanks, that request worked for me too. The request I was using also had
associatedDataPattern
, which I think is causing the issue. Here is the request:
Thanks for the update. But I hope with the request that does work, you should be able to obtain an OAEP certificate - at least we obtained such certs and used those for FIPS validations.
Ciao Stephan
Sounds good to me, thanks Stephan.
Hi,
I'm testing out the KTS IFC implementation and received the following error with the following test case. I got the test case manually from ACVP server and tested on fedora 29's openssl.
Error message
Test case
Thanks, Michelle