From: Bengt Richter <bokr@bokr.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40405@debbugs.gnu.org, Diego Nicola Barbato <dnbarbato@posteo.de>
Subject: bug#40405: System log files are world readable
Date: Tue, 7 Apr 2020 02:49:58 +0200 [thread overview]
Message-ID: <20200407004958.GA8760@LionPure> (raw)
In-Reply-To: <87blo4clpp.fsf@gnu.org>
Hi Ludo,
On +2020-04-07 00:07:14 +0200, Ludovic Courtès wrote:
> Hi,
>
> Ludovic Courtès <ludo@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
next prev parent reply other threads:[~2020-04-07 0:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 13:19 bug#40405: System log files are world readable Diego Nicola Barbato
2020-04-03 13:34 ` Diego Nicola Barbato
2020-04-05 22:12 ` Ludovic Courtès
2020-04-06 22:07 ` Ludovic Courtès
2020-04-07 0:49 ` Bengt Richter [this message]
2020-04-07 7:30 ` Ludovic Courtès
2020-04-08 12:32 ` Diego Nicola Barbato
2020-04-08 19:49 ` Ludovic Courtès
2020-04-19 14:28 ` Ludovic Courtès
2020-04-22 20:04 ` Ludovic Courtès
2020-04-28 13:11 ` Diego Nicola Barbato
2020-04-28 20:57 ` Ludovic Courtès
2020-04-29 10:02 ` Diego Nicola Barbato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200407004958.GA8760@LionPure \
--to=bokr@bokr.com \
--cc=40405@debbugs.gnu.org \
--cc=dnbarbato@posteo.de \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).