FIPS related
Details
Details
Description
Yesterday
Yesterday
werner edited projects for T5964: gnupg should use the KDFs implemented in libgcrypt, added: gnupg26; removed gnupg24.
Let's schedule that for 2.6
Thu, May 25
Thu, May 25
Mon, May 15
Mon, May 15
GnuPG is and can't be FIPS-140-3 compliant due to the way it is implemented. We may eventually employ the new hash-and-sign API of Libgcrypt to move into this direction but that has not yet been done. However, this also requires the use of the new indicator API and the, well, a RedHat kernel.
Fri, May 5
Fri, May 5
werner added a comment to T5691: Release libgcrypt 1.10.0.
If you experience build problems on macOS see T6442
Apr 13 2023
Apr 13 2023
Fixed in 1.10.2.
gniibe closed T5975: Allow signature verification using specific RSA keys <2k in FIPS mode as Resolved.
Fixed in 1.10.2.
Fixed in 1.10.2.
gniibe closed T5919: libgcrypt tests/basic.c and tests/keygen.c occasionally fail with "error generating RSA key: Number is not prime" as Resolved.
Fixed in 1.10.2.
gniibe added a comment to T6127: FIPS 140-3 final review comments.
Fixed in 1.10.2.
gniibe closed T6393: DRBG with SHA384 is no longer allowed in FIPS mode (and looks like impossible to enable anyway) as Resolved.
Fixed in 1.10.2.
gniibe added a comment to T6394: FIPS requires running PCT tests unconditionally.
Fixed in 1.10.2.
gniibe closed T6396: the gcry_pk_hash_sign/verify operates in FIPS non-operational mode as Resolved.
Fixed in 1.10.2.
Fixed in 1.10.2.
gniibe added a comment to T6417: FIPS service indicator regarding the public key algorithm flags and objects.
Fixed in 1.10.2.
gniibe closed T6376: FIPS 140-3: add explicit indicators for md and mac to unblock MD5 in apt as Resolved.
Fixed in 1.10.2.
Mar 24 2023
Mar 24 2023
gniibe changed the status of T6417: FIPS service indicator regarding the public key algorithm flags and objects from Open to Testing.
Pushed the change.
Mar 21 2023
Mar 21 2023
Mar 20 2023
Mar 20 2023
Mar 8 2023
Mar 8 2023
gniibe moved T6376: FIPS 140-3: add explicit indicators for md and mac to unblock MD5 in apt from Backlog to Next on the FIPS board.
gniibe changed the status of T6376: FIPS 140-3: add explicit indicators for md and mac to unblock MD5 in apt from Open to Testing.
Thank you.
Applied to both (master and 1.10).
gniibe changed the status of T6397: PCT failures inconsistency in regards to the FIPS error state from Open to Testing.
gniibe changed the status of T6396: the gcry_pk_hash_sign/verify operates in FIPS non-operational mode from Open to Testing.
gniibe changed the status of T6394: FIPS requires running PCT tests unconditionally from Open to Testing.
gniibe changed the status of T6393: DRBG with SHA384 is no longer allowed in FIPS mode (and looks like impossible to enable anyway) from Open to Testing.
gniibe moved T6397: PCT failures inconsistency in regards to the FIPS error state from Next to Ready for release on the FIPS board.
gniibe moved T6396: the gcry_pk_hash_sign/verify operates in FIPS non-operational mode from Next to Ready for release on the FIPS board.
gniibe moved T6394: FIPS requires running PCT tests unconditionally from Next to Ready for release on the FIPS board.
Mar 7 2023
Mar 7 2023
gniibe moved T6393: DRBG with SHA384 is no longer allowed in FIPS mode (and looks like impossible to enable anyway) from Backlog to Next on the FIPS board.
gniibe claimed T6393: DRBG with SHA384 is no longer allowed in FIPS mode (and looks like impossible to enable anyway).
Applied your patch (from gitlab) to both (master and 1.10).
gniibe moved T6396: the gcry_pk_hash_sign/verify operates in FIPS non-operational mode from Backlog to Next on the FIPS board.
Applied to both (1.10 and master).
gniibe added a comment to T6393: DRBG with SHA384 is no longer allowed in FIPS mode (and looks like impossible to enable anyway).
You are right, there is no way to use DRBG with SHA384 by libgcrypt.
gniibe moved T6397: PCT failures inconsistency in regards to the FIPS error state from Backlog to Next on the FIPS board.
gniibe moved T6394: FIPS requires running PCT tests unconditionally from Backlog to Next on the FIPS board.
Applied to both (1.10 and master).
Applied to both (of 1.10 and master).
Mar 6 2023
Mar 6 2023
tobhe added a comment to T6376: FIPS 140-3: add explicit indicators for md and mac to unblock MD5 in apt.
Right, thanks for the review! Updated patches below.
Jakuje added a comment to T6376: FIPS 140-3: add explicit indicators for md and mac to unblock MD5 in apt.
Actually, the same issue is in the mac case, which I missed on first couple of reviews:
- enum gcry_mac_algos alg = va_arg (arg_ptr, enum gcry_cipher_algos); + enum gcry_mac_algos alg = va_arg (arg_ptr, enum gcry_mac_algos);
Jakuje added a comment to T6394: FIPS requires running PCT tests unconditionally.
We discussed this further with the lab and there are more problematic flags that we need to "cut" and we can not do that always in the code as for example the RFC6979 (deterministic ECDSA signatures) are not allowed in the current version of the FIPS documents, but it is used in the selftests (which is weirdly enough allowed) so we just need to mark it unapproved. Lets discuss this further tomorrow.
Jakuje added a comment to T6376: FIPS 140-3: add explicit indicators for md and mac to unblock MD5 in apt.
Going through the code once more, there is one typo to be fixed:
+_gcry_fips_indicator_md (va_list arg_ptr)
+{
+ enum gcry_md_algos alg = va_arg (arg_ptr, enum gcry_cipher_algos);should say
+_gcry_fips_indicator_md (va_list arg_ptr)
+{
+ enum gcry_md_algos alg = va_arg (arg_ptr, enum gcry_md_algos);otherwise ack.