[Bug 2073429] Re: Jammy clevis forces argon2id for keyslots

2025-03-09 Thread Chris Upchurch
Understood. Reverting tag to verification-needed-jammy since I can't effectively test this. I'm being pushed for > 95% STIG compliance & local won't budge on the FIPS disable call, so I guess I'm still stuck without tpm2 for the time being. ** Tags removed: verification-failed-jammy ** Tags added

[Bug 2073429] Re: Jammy clevis forces argon2id for keyslots

2025-03-09 Thread Chris Upchurch
I did not set OPENSSL_FORCE_FIPS_MODE=0. I'm unable to do so because "just disable FIPS" (even for one-off tasks) would net me CMMC and/or STIG audit failures, the side effects of which I'm not keen on experiencing. I have no issues with other clevis calls on jammy under FIPS (clevis-tang, clevis-s

[Bug 2073429] Re: Jammy clevis forces argon2id for keyslots

2025-03-07 Thread Chris Upchurch
Proposed package update did not fix the issue for me. VERSION TESTED: clevis_18-1ubuntu1.1/jammy-proposed TEST CASE: 1. Select existing workstation running 22.04/jammy with fips-updates enabled 2. Ensure all apt packages are up to date 3. Confirm fips mode is enabled: cat /proc/sys/crypto/fip