From nobody Thu Oct 26 21:36:22 2023 X-Original-To: freebsd-security@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SGfHs0W3Fz4yJR3 for ; Thu, 26 Oct 2023 21:36:25 +0000 (UTC) (envelope-from des@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SGfHr71Q9z3Ywk; Thu, 26 Oct 2023 21:36:24 +0000 (UTC) (envelope-from des@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698356185; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pFRXQTV+Jtvjt5PQFS9O+iPnSGXHH83kL+wuK6fZ7Og=; b=RdFv3J5Q3GsERkz3VTUxMpwLjv+MqzEhe5HsmGWkOIcPZ2EVt0v3EuOwXr2CpSKtVBnus5 APXX5+wVsgwnfXagdda6m5HdXT7YKabmInPxz8zcljSP+LoLuicnHlk4g5G7qsvQ92cMEN JTjOWAsm8SIU9OmrTShIrmR5sVdeMdny13RDtvn8e19v3FeZC/J3HBuaPQ6RhshUW5TLqt Ux0yTBZCxge1hYT2PEizn7Gvubi7Ekp1Q4P/j06MAeoh/sMb8zsm3UO91SSFaZ4E0jRRmu i2mteqjq7SnIm3jJCqs4/XyUvxRGtUEj9i3ba9L2WdMI5ENuvqwoKoSdnHwcgA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698356185; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pFRXQTV+Jtvjt5PQFS9O+iPnSGXHH83kL+wuK6fZ7Og=; b=Ek35b2KU6cpz3/vCH6RyxcvEdfpu37CHA6UUacQ5NZ0x2cLZxMc1bCbLFlvvv2L6p4eNya TPbC2/NFfmCWOJHWiqztbu5I6uxT1lA0PUiWD8Cce5tDu8v5fSMIvIWvsjotATVU7TNepi 15LGBKp5kMt0v6JaylwMuulfDAKh11bAyc3qaadOdmHdCtG6QkkUdwzHclG1ZJ/5kdjyDP Votp1djv76n4TMTGnzMrLffNZt1sRiUiWttqJZ8VDPAMRp4TvWBh/2gy3E40qWIeY7evjn DelexwHz2RNYRu3u1OJMIpwne2FkT3I5434Lc6kpiP9ZS1CLoy+1CVFSjdMapQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698356185; a=rsa-sha256; cv=none; b=J40bkdxukmTogNQoW4kdsmnDimdf857Rcatw+T9IaX1JJHpus3WXZW6QtfOxydfBuQExKP 6UnudkGiOInrGnROcEz99aqWoYJ14ymBmkMiCKI2optPZ8SSItH+Eg5qrfI4lQOZVFj7Oi I4S2tS+T/9MB6xdLhV1kXx/hHy7BEdnBriQ0ZFuJxdVfLFga7LvP7O6ZIjXK7jeqGJmTVm wMqdFJb1nrznnJSGatNTrsFRVDtt+zW3xobvZa0gN3Z9tyI9EuBoMa7Iih/r5YixsXJ9n/ K0bOq4CDra+Z5VGeKQT93XsARXkmen8QFZ9tKhCXaGxZADgqWYhRY8CLX1Mefg== Received: from ltc.des.no (48.115.65.81.rev.sfr.net [81.65.115.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: des) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SGfHr5Nm8z1SVC; Thu, 26 Oct 2023 21:36:24 +0000 (UTC) (envelope-from des@freebsd.org) Received: by ltc.des.no (Postfix, from userid 1001) id 03DBFEFAE3; Thu, 26 Oct 2023 23:36:23 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: void Cc: freebsd-security@freebsd.org Subject: Re: securelevel 1 In-Reply-To: <35f733cc-a6c2-46a4-b564-b1ef87893fc5@app.fastmail.com> (void@f-m.fm's message of "Tue, 24 Oct 2023 17:33:22 +0000") References: <6638DADD-FCDB-492C-B1E8-441C6622038B@FreeBSD.org> <663fd243-94ec-40c1-ac66-ca8e3d5f278d@quip.cz> <35f733cc-a6c2-46a4-b564-b1ef87893fc5@app.fastmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Date: Thu, 26 Oct 2023 23:36:22 +0200 Message-ID: <86ttqd12y1.fsf@ltc.des.no> List-Id: Security issues List-Archive: https://lists.freebsd.org/archives/freebsd-security List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-security@freebsd.org X-BeenThere: freebsd-security@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable void writes: > In order to accomplish what I'd like, I understand that I'd need to set += schg > on the individual logs, then set the securelevel afterwards and reboot. If you set the log file +schg, it can't be written to at all. That's obviously not what you want. If you set it +sappnd, it can be written to, and newsyslog will be able to rotate it; an attacker with superuser privileges will also be able to replace it with a doctored file. There is no way to allow one without the other. The usual solution is to log to a remote machine. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org