Hello Martin, Martin Pitt <mp...@redhat.com> writes:
>> > Eek, thanks for reporting! I filed >> > https://github.com/cockpit-project/cockpit/issues/16450 about this, and >> > added >> > it to our current quarterly plan, this is quite important. The above >> > schema for >> > copying the cert to /run ought to take care of the reading permission >> > issues, >> > but of course certmonger needs to be able to write the cert in the first >> > place. >> >> Great! Thanks for opening the issue and tracking it. > > I had a first stab at this in > https://github.com/cockpit-project/cockpit/pull/16453 > I still need some help from our SELinux developers to fix the policy, but > after > that this should work quite a bit better. I've tried it on Debian with current cockpit and added a comment to the pull request. In short: we are not there yet, but I like to new documentation much better. Jochen -- This space is intentionally left blank. _______________________________________________ cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org To unsubscribe send an email to cockpit-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/cockpit-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure