Bug 2369823 - After upgrade to 6.16.0-0.rc0.250530gf66bc387efbe.7.fc43, no file /proc/sys/crypto/fips_enabled
Summary: After upgrade to 6.16.0-0.rc0.250530gf66bc387efbe.7.fc43, no file /proc/sys/c...
Keywords:
Status: CLOSED DUPLICATE of bug 2369735
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-02 15:43 UTC by Florence Blanc-Renaud
Modified: 2025-06-03 10:09 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-06-03 10:09:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Florence Blanc-Renaud 2025-06-02 15:43:41 UTC
1. Please describe the problem:
After upgrading the kernel to kernel-core-6.16.0-0.rc0.250530gf66bc387efbe.7.fc43.x86_64, the file /proc/sys/crypto/fips_enabled does not exist any more

2. What is the Version-Release number of the kernel:
6.16.0-0.rc0.250530gf66bc387efbe.7

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
With kernel-core-6.15.0-0.rc7.58.fc43.x86_64 the file was present.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Install a rawhide machine with the specified kernel, then
# cat /proc/sys/crypto/fips_enabled
cat: /proc/sys/crypto/fips_enabled: No such file or directory


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes

6. Are you running any modules that not shipped with directly Fedora's kernel?:
no

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

The file /proc/sys/crypto/fips_enabled is used in order to check if the system is in FIPS mode (contains 1) or not (contains 0). If the file is missing, many executables fail.

Reproducible: Always

Comment 2 Alexander Bokovoy 2025-06-03 10:09:06 UTC

*** This bug has been marked as a duplicate of bug 2369735 ***


Note You need to log in before you can comment on or make changes to this bug.