Your message dated Mon, 8 Jul 2024 18:26:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#1032381: aide: Broken aideinit due to _aide user
handling
has caused the Debian Bug report #1032381,
regarding should depend/suggest libcap2-bin for non-systemd systems
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1032381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032381
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aide
Version: 0.18-2
Severity: serious
Hi!
Just upgraded a server to Debian bookworm, and noticed that aideinit
was not working anymore, giving the following error:
,---
# aideinit --yes --force
Running aide --init...
User [_aide] not known
AIDE --init return code 1
`---
This specific system is using sysvinit. Checking the postinst I notice
it is conditionally using systemd-sysusers if available, but then
unconditionally tries to chown files and does not fail if it cannot
perform the operation.
So ideally this would get adduser support, and depend on either that
or systemd-standalone-sysusers.
After having manually created the user with adduser, then aideinit
still failed with:
,---
# aideinit --force --yes
Running aide --init...
/bin/bash: line 1: /var/log/aide/aideinit.log: Permission denied
AIDE --init return code 1
`---
Checking «/var/log/aide/» I saw that at least aideinit.log and
aideinit.errors were indeed still owned by root:adm, fixing the
ownership for those files made aideinit work again. So I guess this is
also missing in the postinst handling.
Thanks,
Guillem
--- End Message ---
--- Begin Message ---
On Tue, Oct 03, 2023 at 04:15:29PM +0200, Marc Haber wrote:
> I plan to close this bug by the End of October 2023.
Doing so now.
--- End Message ---
