As a result of 1274150 et al., it is likely the case that krb5 components should not error on: - Inclusion of nonexistent files - Inclusion of nonexistent directories - Broken symlinks in extant directories Up for additional debate is what we should do about files/directories that exist but have incorrect permissions. (I think we should probably still error out here, but could be convinced otherwise.)
This bug is also in older versions of fedora and not just in rawhide.
Well, it's present on all of them because krb5 has never cared about this kind of issue before. rawhide or 23 is as good as any version to assign this to.
I got to a case where a fresh krb5 package was installed together with too old crypto-policies package. In this case I think it is correct that krb5 calls fail. What would be appreciated is setting a dependency on specific crypto-policies version. krb5 expected /etc/krb5.conf.d/crypto-policies, but this symlink didn't have the target location. The result were failing test in the sssd package.
Attaching downstream tkt: https://bugzilla.redhat.com/show_bug.cgi?id=1317601
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
The bug still exists and can cause more problems in container world. Especially if someone bind mount krb5.conf and krb5.conf.d but forget to symlinks.
If someone has forgotten the symlinks, it would be better to fail out immediately so they know to fix them. Otherwise, if there was data there, it will not be read, and krb5 will behave in unexpected ways.