Hi Ludo, On +2020-04-07 00:07:14 +0200, Ludovic Courtès wrote: > Hi, > > Ludovic Courtès <l...@gnu.org> skribis: > > > In the meantime, the patch below fixes the syslogd problem. Also > > attached is a patch for the accounting database, though that one is > > questionable. > > I pushed the syslog bits along with a test as commit > d7113bb655ff80a868a9e624c913f9d23e6c63ad. (I think already > world-readable files will remain world-readable though?) >
Could build daemons do some kind of maintenance rebuild to chmod them? And maybe be scheduled to monitor new files for other mistakes as well? Meanwhile, could a superuser chmod them without affecting hashes? (curious as to whether permission bits escape hashing). > The main remaining issue here is log files created by > ‘fork+exec-command’. We’ll have to address that in the Shepherd proper, > I think. > > Ludo’. > > > -- Regards, Bengt Richter
