From patchwork Mon Apr 22 16:44:00 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Peter_M=C3=BCller?= X-Patchwork-Id: 7754 Return-Path: Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature ECDSA (secp384r1)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4VNWL50PDNz3wvs for ; Mon, 22 Apr 2024 16:44:13 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature ECDSA (secp384r1)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4VNWL41DcFzvx; Mon, 22 Apr 2024 16:44:12 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4VNWL40lDsz32wK; Mon, 22 Apr 2024 16:44:12 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature ECDSA (secp384r1)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4VNWL23LGgz32t8 for ; Mon, 22 Apr 2024 16:44:10 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4VNWL05hT7zXy for ; Mon, 22 Apr 2024 16:44:08 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1713804249; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WhSuNhQmJDHq4+rzvTRuzkU763856R3E6dCdUZR7KxU=; b=oP5DISxlHM7sResscPd60ndX+1RVq1ll1JRlldlQ9V4s0fXmlVI2UVdLipyk/5WPEd2KZF 7Las1IT3w6coWvBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1713804249; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WhSuNhQmJDHq4+rzvTRuzkU763856R3E6dCdUZR7KxU=; b=wtXRFBwtgpKL7u0KzhU075aYXjLNUaX1hz4nrMt5EtM189IBSoj15/gM9cKN9RBU+Lt7q4 TVnQRtF167CzBj8hAx5qtkRaZRGrAez3+bZ0ZzeqXSSiWfWHdChNlqGmqkSaSO+RjR/NjB sKapgvQ4JE19dFA5G0/yLo2eKNYtnkyD9ZOwHYL4ba62jB798VsktYgEEg0PMvE35HptZ5 0l/ObQ3lnCQ8NerZLrrK2MFtLjf85o7WHja6sjLd9fjPvb2UaCpBXyFV8aVwaEHChzpEW9 cMPhfOkcomh86LrS0iiBaUzhVJ9JR68gn2ik5fL7MLPRgHdiZrELDe03tlj0fg== Message-ID: <323d35e9-a5ea-4967-8e98-9299aebff868@ipfire.org> Date: Mon, 22 Apr 2024 16:44:00 +0000 MIME-Version: 1.0 Subject: [PATCH 3/3] suricata.yaml: Fix Landlock path settings To: development@lists.ipfire.org References: <0a12ec92-7119-4c7f-aafc-9257cbec1ff8@ipfire.org> From: =?utf-8?q?Peter_M=C3=BCller?= In-Reply-To: <0a12ec92-7119-4c7f-aafc-9257cbec1ff8@ipfire.org> Message-ID-Hash: CQNJ3QWICD3OAIKLZSPYJ2Y32BDGHSZ7 X-Message-ID-Hash: CQNJ3QWICD3OAIKLZSPYJ2Y32BDGHSZ7 X-MailFrom: peter.mueller@ipfire.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list List-Id: IPFire development talk Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Suricata will complain if it cannot read its own configuration file, hence read-only access to /etc/suricata must be allowed. Since the list applies to directories, rather than files, restricting read access to only /usr/share/misc/magic.mgc is not possible; reading /usr/share/misc must be allowed instead. Fixes: #13645 Tested-by: Peter Müller Signed-off-by: Peter Müller --- config/suricata/suricata.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml index b57a1d9d4..faa1aa71d 100644 --- a/config/suricata/suricata.yaml +++ b/config/suricata/suricata.yaml @@ -775,7 +775,8 @@ security: # /usr and /etc folders are added to read list to allow # file magic to be used. read: - - /usr/share/misc/magic.mgc + - /etc/suricata + - /usr/share/misc - /usr/share/suricata - /var/ipfire/suricata - /var/lib/suricata