From nobody Tue Sep 03 17:42:34 2024 X-Original-To: net@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 4WytHr5cGbz5TfX7 for ; Tue, 03 Sep 2024 17:42:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WytHr1X3jz4FCj for ; Tue, 3 Sep 2024 17:42:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1725385368; a=rsa-sha256; cv=none; b=xY8Zwk1FyGVFL5MaxIbsBatN+pEiWO00JL3y7jPyfH9rbX2QKV/3w2MPsmUZPcr6v3HYK6 nCnfkuzbRlwJnv7H79d2RrsEIZWGrd67v2a7Xi4WhIC4Z9VLBCs3iblDq7Bz0ydtH2xK4d JqjFwOr6VCaOs3JWoSUZxVs+ww6kyEBUW58eGKXasaA9UIn6OJZxRyKnngTvyK4cPxfEfF yDhoEpb2j8jk6ftfLApBCSBRWH0J/B0250pLL1kxtey9/GiTdqz9rIyjLIKK6+YMFA3JTI e4LuS0jcAaj461+i8SZkINe00yl87ly8FVJ2B4xUSOmxd7Pi2m1JG7Oxkr61eA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1725385368; 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=0ahaZX96S2o+AyzMupXwAt40dTs6qQv84Uiki2Wi/TE=; b=uwf1C6sG2zlBHe4aAIhXlpjG/89n4m5tkGHgh56K+6sG0QiGs567g6hVPWYAYPWGpNrXXh 1Zb2l9mbUmjk3kUo+foz/bGKFsAhpFf5muh2OnSpkYaDq54If2dy3JieEEwWiF6Y5IKr6b 3Rr87cIh2lk5PWmXCeqZ4EQoxYDejibR1AJM64O1VTh9S3PKe4QlrTZsQsga2Dg7i2XcCQ N5IRGX/KSaEE7dCLp/A4XkWQrJ4VFXckBYdPoCmLaEm47gmQYBpmfjPyX/+V4mM7157Sbq XJzyisXuDxv4DE8q6gtyXHPfwO+uz2mGVlAcbzlEPw1Bb1B4tn9UGNWfay9VcA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4WytHr17n6zqWr for ; Tue, 3 Sep 2024 17:42:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 483HgmY3023273 for ; Tue, 3 Sep 2024 17:42:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 483Hglt1023221 for net@FreeBSD.org; Tue, 3 Sep 2024 17:42:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 280701] FreeBSD-SA-24:05 fix breaks ICMP/ICMP6 states handling in pf firewall (ping, traceroute) Date: Tue, 03 Sep 2024 17:42:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gordon@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280701 --- Comment #65 from Gordon Tetlow --- In reply to doktornotor from comment #64: > Not sure about other people here suffering from the regressions, but I'd > seriously appreciate some form of communication beyond automated > commit-hook@ messages. While I can't address the rest of this comment, in regards to more communication, secteam will publish an erratum for this issue shortly. We a= re letting it sit for a hot minute to ensure we don't have (additional) breaka= ges. As you can imagine, the last thing we want to do is issue an erratum for an erratum. There was also a question earlier from comment #40: > How's this whole thing a security issue deserving an SA and urgent patchi= ng > causing the above regressions which are impacting real network operation = and > many users, goes beyond me, sorry.=20 As to the question of why the original "fix" was treated as a security advi= sory =E2=80=93 The issue was originally brought to us by an external researcher = (as credited in the SA-24:05.pf write up) as a security issue, so there was an anchoring bias. secteam did have a debate internally as to whether it should be a security advisory or an erratum. Ultimately, we decided to call it an SA du= e to the fact that security software on the system was behaving in an unexpected= way and allowing things through that it shouldn't have. I, with my security-off= icer hat on, stand by this decision and would likely make the same one given the same facts today. --=20 You are receiving this mail because: You are the assignee for the bug.=