Description of problem: Install using the Anaconda Web UI Preview ISO, but do it with fips=1 on the command line, then start Fedora with fips=1, and set a short (3 character) password. On startup, gnome-keyring-daemon aborts. This may be due to the short password, and maybe we do not need to fix this, since nobody should use short passwords in FIPS mode. Version-Release number of selected component: gnome-keyring-42.1-2.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: /usr/bin/gnome-keyring-daemon --daemonize --login crash_function: _gcry_logv executable: /usr/bin/gnome-keyring-daemon journald_cursor: s=bd425fc93ebd4fe1b93a267002ccd966;i=867;b=5346a975f80b4580b561f8715c31d61d;m=390f5a4;t=5ef19266a3e65;x=fb416e344150f3c8 kernel: 6.0.9-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 2093705
Created attachment 1930163 [details] File: backtrace
Created attachment 1930164 [details] File: core_backtrace
Created attachment 1930165 [details] File: cpuinfo
Created attachment 1930166 [details] File: dso_list
Created attachment 1930167 [details] File: environ
Created attachment 1930168 [details] File: limits
Created attachment 1930169 [details] File: maps
Created attachment 1930170 [details] File: mountinfo
Created attachment 1930171 [details] File: open_fds
Created attachment 1930172 [details] File: proc_pid_status
Actually, the problem is likely that https://github.com/GNOME/gnome-keyring/blob/master/pkcs11/secret-store/gkm-secret-binary.c#L639-L640 uses GCRY_MD_MD5, which it shouldn't, and which will not work in FIPS mode.
It would require updating the keyring format to fix this properly. We made some effort in libsecret to define the format version 1, and the plan was to replace the gnome-keyring-daemon with a secret-service daemon provided by libsecret (bug 1899998), though the work has been stalled for quite some time for lack of resources. One of the tricky parts is migration of the existing data, but if this bug only affects Anaconda for new user, there might be an option to bypass gnome-keyring-daemon, e.g., using the local file storage provided by libsecret, or some other means.
This does not affect anaconda, this happens after installation on first startup (and probably every startup after that). Since this code is probably also on RHEL 9, this would mean that gnome-keyring cannot be used on systems in FIPS mode on RHEL 9.
Similar problem has been detected: Vyt reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: /usr/bin/gnome-keyring-daemon --daemonize --login crash_function: _gcry_logv executable: /usr/bin/gnome-keyring-daemon journald_cursor: s=ef4e23ffd9bf4938b7231ffe62a22198;i=2c733;b=828a9ca124df4dae824b8392b59d2f10;m=2a8af94;t=5f2648de64335;x=3e5e76ac4c9f114d kernel: 6.0.17-300.fc37.x86_64 package: gnome-keyring-42.1-2.fc37 reason: gnome-keyring-daemon killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.