Skip to contentSkip to conversation

rfc4543 testvectors in testmgr.h kernel

DISCUSSION Jussi Kivilinna 2 participants 2 messages Feb 10, 2015 – Feb 11, 2015 1 message not in the archive Crypto API

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 4 lines · Marcus Meissner

Hi Jussi,

We were trying to use rfc4543(gcm(aes)) in the kernel for FIPS mode, but the testvectors seem to fail.

You probably need to add '.fips_allowed = 1,' in testmgr.c for "rfc4543(gcm(aes))" to enable algorithm in fips mode.

Quoted 4 lines

Did you verify that they work? Are these the ones from Page 18 of
https://tools.ietf.org/html/draft-mcgrew-gcm-test-01, as there the "plaintext" and "aaad" seem to be switched?

rfc4543() wrapper constructs the aad from '.assoc' and '.input'.

-Jussi

Quoted 3 lines

Ciao, Marcus

#2 lore raw
Quoted 6 lines · Jussi Kivilinna
Quoted 4 lines · Marcus Meissner

Hi Jussi,

We were trying to use rfc4543(gcm(aes)) in the kernel for FIPS mode, but the testvectors seem to fail.

Quoted 8 lines

You probably need to add '.fips_allowed = 1,' in testmgr.c for "rfc4543(gcm(aes))" to enable algorithm in fips mode.

Quoted 4 lines

Did you verify that they work? Are these the ones from Page 18 of
https://tools.ietf.org/html/draft-mcgrew-gcm-test-01, as there the "plaintext" and "aaad" seem to be switched?

rfc4543() wrapper constructs the aad from '.assoc' and '.input'.

We tried above and still got -2 errors.

I think "ecb(cipher_null)" also needs to set the .fips_allowed flag, so that the rfc4543 setup can pull it in.

CIao, Marcus