From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#40405: System log files are world readable Date: Tue, 07 Apr 2020 09:30:29 +0200 Message-ID: <87zhbnbvmy.fsf@gnu.org> References: <87v9mg1zbt.fsf@GlaDOS.home> <874ktxh99k.fsf@gnu.org> <87blo4clpp.fsf@gnu.org> <20200407004958.GA8760@LionPure> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42499) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jLihL-0000vP-7A for bug-guix@gnu.org; Tue, 07 Apr 2020 03:31:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jLihK-0002bm-BX for bug-guix@gnu.org; Tue, 07 Apr 2020 03:31:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37954) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jLihK-0002bY-8f for bug-guix@gnu.org; Tue, 07 Apr 2020 03:31:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jLihK-0003Op-62 for bug-guix@gnu.org; Tue, 07 Apr 2020 03:31:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20200407004958.GA8760@LionPure> (Bengt Richter's message of "Tue, 7 Apr 2020 02:49:58 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Bengt Richter Cc: 40405@debbugs.gnu.org, Diego Nicola Barbato Hi, Bengt Richter skribis: > On +2020-04-07 00:07:14 +0200, Ludovic Court=C3=A8s wrote: >> Hi, >>=20 >> Ludovic Court=C3=A8s skribis: >>=20 >> > In the meantime, the patch below fixes the syslogd problem. Also >> > attached is a patch for the accounting database, though that one is >> > questionable. >>=20 >> 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? Yes, we could do that, I just haven=E2=80=99t checked if this is necessary = or thought about how to do it. > Meanwhile, could a superuser chmod them without affecting hashes? Definitely. (There=E2=80=99s no =E2=80=9Chashing=E2=80=9D involved for /va= r/log.) Ludo=E2=80=99.