[pkg-bacula-devel] Bug#843838: Bug#843838: Bug#843838: Bug#843838: Fail to access config file

[Sven Hartge]

On 10.11.2016 18:51, Jörg Frings-Fürst wrote:

> I guess that the error is the wrong group.

Of course, this is obvious.

> But the error comes not from use rsync without --numeric-ids.
> I don't use rsync, I have moved the hard disk with dd.
> 
> But also I have no idea from where the dirmngr comes.

I also have no idea, but I find it very suspicious that every group that
should be "bacula" is "dirmngr" on your system, as if someone/something
changed /etc/group or replaced it with a one not belonging to the system.

> A note:
> 
> If you change "the way the daemons are started" please check and change
> the required user/group.

I tested this change on several systems, some newly installed Sid, some
upgraded from Jessie, some even upgraded from Squeeze and older.

Every sane system had the correct groups and users for /etc/bacula/*.

The only change for permissions and owners was needed for
/etc/bacula/bacula-sd.conf and this is done in bacula-sd.postinst.

In my opinion this problem is not a bug in the bacula package but your
system was broken to begin with and this change just exposed it.

You need to find out who or what made the changes to /etc/group as more
problems may linger.

I personally also don't see an obligation for Debian packages to check
every possible angle an administrator could have manually broken their
system and try to work around this, but YMMV.

Just broadly changing and overwriting every permission in /etc/bacula/
is also wrong, as the administrator might have made working changes
which we don't want to destroy.

Grüße,
Sven.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20161110/364ddcb9/attachment-0001.sig>