#889009 postfix: /etc/systemd/system/postfix.service.d/override.conf is not world readable

Package:
postfix
Source:
postfix
Description:
High-performance mail transport agent
Submitter:
Daniel Kahn Gillmor
Date:
2024-12-03 09:45:01 UTC
Severity:
normal
#889009#5
Date:
2018-02-01 06:33:10 UTC
From:
To:
check out these permissions:

0 root@alice:~# ls -la /etc/systemd/system/postfix.service.d/override.conf
-rw------- 1 root root 66 Jan 23  2017 /etc/systemd/system/postfix.service.d/override.conf
0 root@alice:~#


and yet, there is nothing secret in the file:

0 root@alice:~# cat /etc/systemd/system/postfix.service.d/override.conf
[Unit]
After=network-online.target
After=systemd-resolved.service
0 root@alice:~#

shouldn't this file be created in mode 0644?  no other override.conf
files are unreadable by "other" on this system.
#889009#10
Date:
2018-02-01 15:59:12 UTC
From:
To:
I note that this shows up in the journal as:

    Configuration file /etc/systemd/system/postfix.service.d/override.conf
    is marked world-inaccessible. This has no effect as configuration data
    is accessible via APIs without restrictions. Proceeding anyway.

so systemd is complaining about it too :/ fixing this would also cut out
the noise there.
#889009#13
Date:
2018-02-02 06:37:28 UTC
From:
To:
Actually, if you have that file, then something else is going on.  It was
removed from the package May 17th of last year both in unstable and
experimental, so I'm not sure why you still have it at all.

Scott K
#889009#18
Date:
2018-02-04 02:40:30 UTC
From:
To:
me neither, but if you've got any suggestions for how i could track it
down, i'm happy to pursue them.

or, if you'd just prefer that i remove it and we close this bug as a
mystery, i can deal with that too.  let me know what you prefer.
#889009#21
Date:
2018-02-04 18:27:41 UTC
From:
To:
It would be worth doing to install 3.2.0-1 from snapshot.d.n and then upgrade
to see if you can replicate the file not being removed.  Unfortunately, my
workflow is all organized around chroots and systemd refuses to start daemons
in chroots, so I don't have an easy way to try this.

If it did stick around, I'd be a little reluctant to just rm -f it in the
postinst since I don't know if I might be removing any local changes people
have made.

What do you  think?

Scott K
#889009#26
Date:
2024-12-03 09:40:07 UTC
From:
To:
Version: 3.1.4-6

This was a leftover after #851521, it looks like.

At any rate, for a few debian releases, postfix does not add this override,
so the issue does not exist anymore.

Let's close this bug report finally.

Thanks,

/mjt