----- Original Message -----
> From: Cyril Brulebois <k...@debian.org>
> Date: Friday, July 12, 2019 06:45:08 PM CDT
> Subject: Re: Bug#911604: haveged start up fails due to apparmor
denying write access to /run/haveged.pid
> To: Axel Beckert <a...@debian.org>, 911604 <911...@bugs.debian.org>
> CC: Gert <t...@gert.gr>, Dean Hamstead <d...@fragfest.com.au>, Justin
Pasher <just...@distribion.com>
>
Everyone: please deploy -8 (just uploaded) to your buster and/or
unstable systems and report back. I've tested this on a stretch system
that's running with systemd, using the daemon directly, or a hacked up
init script to make sure I was evading the initscript→systemd machinery
through LSB functions; and everything looks good with the patch.
But I'd be very happy to have success reports from sysvinit users before
considering backporting this to buster.
Cheers,
Hello,
I use sysvinit. I've installed the 1.9.1-8 version of the package, and
it seems to work properly for me. For reference, I did the following test:
1. Blank out /etc/apparmor.d/local/usr.sbin.haveged to remove my added line
2. /etc/init.d/haveged stop
3. aa-enforce /usr/sbin/haveged
4. /etc/init.d/haveged start -- It failed to start (as expected)
5. Update to haveged=1.9.1-8
6. Verify haveged has started (the post install scripts take care of
apparmor and starting the process)
7. Verify /etc/apparmor.d/local/usr.sbin.haveged is still blank
8. Reboot and verify haveged still starts up properly
Thanks for the quick turn around!
Justin Pasher
