[Dnssec-trigger] current status?
thozza at redhat.com
Thu Mar 12 08:20:28 UTC 2015
On 03/11/2015 08:21 PM, Chuck Anderson wrote:
> What is the current status of dnssec-trigger? Does anyone here run
> this daily on Fedora 21?
> Every day after resuming from suspend, I have crash messages pop up on
> Fedora 21 from dnssec-trigger (even after I fixed rhbz#1187371 myself
> over a month ago).
> Now, I have SELinux problems with dnssec-trigger writing to /etc. The
> current selinux policy apparently doesn't allow this, so I end up with
> no /etc/resolv.conf at all.
> I'm very concerned about this:
> when it seems that even trivial-to-fix bugs like this one go unfixed
> for weeks:
> Other bugs also not fixed:
> and a new one I just filed today for more SELinux issues:
I'm also using dnssec-trigger on Fedora 21 every day, with VPN and
SELinux in enforcing mode. But my Fedora is also upgraded from older
Sometimes my system also ends up without resolv.conf due to
https://bugzilla.redhat.com/show_bug.cgi?id=1195752 . But other
than that, the experience is pretty seamless.
We deferred the Fedora Change to Fedora 23, to sort out these issues.
Lately we had some higher priority issues to deal with, but we are
aware of the status in Fedora and are planning to address all the
Thank you for filing bugs and for adding them to the tracker bug.
Feel free to reach to us directly by email, here on the mailing list
or via Bugzilla.
Software Engineer - EMEA ENG Developer Experience
Red Hat Inc. http://cz.redhat.com
More information about the dnssec-trigger