Done by T7649: gnupg: Use KEM interface for encryption/decryption
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Tue, Jun 17
Tue, Jun 17
• gniibe closed T5964: gnupg should use the KDFs implemented in libgcrypt, a subtask of T6191: FIPS: Supporting running FIPS enabled machine, as Resolved.
May 26 2025
May 26 2025
• gniibe changed the status of T5964: gnupg should use the KDFs implemented in libgcrypt, a subtask of T6191: FIPS: Supporting running FIPS enabled machine, from Open to Testing.
• gniibe changed the status of T5964: gnupg should use the KDFs implemented in libgcrypt from Open to Testing.
May 11 2025
May 11 2025
Included in 1.11.1.
Mar 13 2025
Mar 13 2025
Dec 12 2024
Dec 12 2024
Here are changes for gcry_md_open and its friends.
0001-fips-Change-the-internal-API-for-new-FIPS-service-in.patch4 KBDownload
My idea in https://dev.gnupg.org/T7338#195529 doesn't work well when a function call is done multiple times.
Assuming SUCCESS, and marking all non-compliant places in the code works, and it would be good because libgcrypt so far maintains non-compliant path with rejection.