From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2DF1D3858D39; Mon, 2 Jan 2023 16:36:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2DF1D3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672677411; bh=URRg/I0Lz5Pc4bAf3CVYQtA22Sx98ikk9fJykk5jnW0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=IpV/XsFyvz0Eoj7biZGAE3R8OaYPfx+eXcH25dIW8ymscse66w8DpNkl0XDzLEu8g nNy8Xce8pA9HeIOFgv32lDkjonQuV7RHCBQ5XoWUn0ZQeiHWhw4fL0iSEuJC8fPLWW OsIO7KIC7AHgReGL685YoR1QRPJ8YynJDqSmlqPM= From: "fche at redhat dot com" To: overseers@sourceware.org Subject: =?UTF-8?B?W0J1ZyBJbmZyYXN0cnVjdHVyZS8yOTcxM10gUGxlYXNlIG1ha2Ug?= =?UTF-8?B?bGliYy1hbHBoYSBtYWlsaW5nIGxpc3QgY29tcGF0aWJsZSB3aXRoIOKAnGdp?= =?UTF-8?B?dCBhbeKAnQ==?= Date: Mon, 02 Jan 2023 16:36:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- 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: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29713 --- Comment #35 from Frank Ch. Eigler --- > This is somewhat disappointing since this seems against the spec. These > headers shouldn't be included by default if they aren't set on the origin= al > outgoing message. The RFC4871 standard allows more and non-existent headers to be signed. I suppose one argument is that signing non-existent headers protects email against later insertion of such headers. Characterizing this default as "wrong" or a "misconfiguration" in need of a "fix" is a little too far. Th= ey are inconvenient for the efforts associated with this PR, that's all. --=20 You are receiving this mail because: You are the assignee for the bug.=