IETF Logo Mail Archive

Re: [Ietf-dkim] Headers that should not be automatically oversigned in a DKIM signature?

Dave Crocker <dhc@dcrocker.net> Mon, 05 February 2024 17:47 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83D05C14F5FB for <ietf-dkim@ietfa.amsl.com>; Mon, 5 Feb 2024 09:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L0QTChYiBE7R for <ietf-dkim@ietfa.amsl.com>; Mon, 5 Feb 2024 09:47:43 -0800 (PST)
Received: from buffalo.tulip.relay.mailchannels.net (buffalo.tulip.relay.mailchannels.net [23.83.218.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5E1DC14F601 for <ietf-dkim@ietf.org>; Mon, 5 Feb 2024 09:47:43 -0800 (PST)
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id A8344105DC5 for <ietf-dkim@ietf.org>; Mon, 5 Feb 2024 17:47:42 +0000 (UTC)
Received: from nl-srv-smtpout2.hostinger.io (unknown [127.0.0.6]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id EA418105D9C for <ietf-dkim@ietf.org>; Mon, 5 Feb 2024 17:47:41 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1707155262; a=rsa-sha256; cv=none; b=0lqh6fBns9c4b8dcr4IDRpaZVaj4ThfoOMs5KGMyhxS/PgsclYsT511kPFCHF/w3S96Nzt zrRDqAocl0zZ+QObcGWNo3QVYK+pTd0XPpsfK9aeAvKB5hgH0MmKhSjFZJOcYq8UENyAtX vOknDsvrdPNGLGhRszA9vFxTIxb60Nejf4bEw1ug/CTRor7n2EKsTfj/UoU7tyIjeb00p1 Yju7HvOV9x+ariquHit5kRrIQRK2bKHwpVPUVexlyTNpCu0F8gqXAar3m57P9ZDLreJHr5 jtDc6qiP6HbINz64kV9OHkp4h3B/HxognqNJgZXokfQj4/UBwQ+uMWWG3xPkZg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1707155262; h=from:from:reply-to: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:dkim-signature; bh=tObdJ/Ma9u8ctFEP5UfnKixPUClQq80gOih+5L0c0xw=; b=uK3V8M2B2yA6R4LaY8X9iOzxPPLXE+a1XyaI2+pTG4+PvNSknVokndAI2lv63130S/RjMM bfRdiyrSTcrb3yIZL3jZznai561v4YjQIP0YRX5b8msRdNUDrbP33G/53XPoKKNVdnRMyD rpuXF6vQ8upV4l7t/STlGW/blWGrcnRHxQ4v0/4MYA1i8qeSczJDgh7aaG4HZdPyz0UXNf dIkFZlqdcP/jQC7pWPHH9mF9NUCe8ChiqxnNnkwhO6r0EGciTYXRKCgpBbEE0HPui/GN4h PHJ+ZUCiWejQkrAsLiT3D5ghevZgvqEmyUoHvO/drA4PPA0MhnREfrdveqgIKw==
ARC-Authentication-Results: i=1; rspamd-55b4bfd7cb-xv6s7; auth=pass smtp.auth=hostingeremail smtp.mailfrom=dhc@dcrocker.net
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authuser|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Arch-Decisive: 5b6aa3e02945549f_1707155262459_390015502
X-MC-Loop-Signature: 1707155262459:513233633
X-MC-Ingress-Time: 1707155262459
Received: from nl-srv-smtpout2.hostinger.io (nl-srv-smtpout2.hostinger.io [145.14.150.88]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.100.20.149 (trex/6.9.2); Mon, 05 Feb 2024 17:47:42 +0000
Message-ID: <e59bbaa2-945c-4ed8-85b4-3a79ebc8bfbd@dcrocker.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1707155260; h=from:from:reply-to: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=tObdJ/Ma9u8ctFEP5UfnKixPUClQq80gOih+5L0c0xw=; b=KTTm0o4gESUsEGtuiuA0LQDzFDPAyM9khA84MLDi0/1xe0YgXJ6bQgCbk9t3YnMFhH7v14 y/6kfOoiE0etFLZHbVf6AOslFpdB3GFnqtvi2YNj7nRpapOojNpy9F7mryhD9KXYSzAzmq N9+myGoUd2W7odb6F8qLAdAXyZp6T+uPPEF5sOvHIz0b6w8VhQHWW2XO7tGeu6NnsX1mL+ Fb6QR7M+hMre540WStfc6vruNSkiPsILP3Lk/fMR8inQcr7JLbFpyOB+zSIkmx7Da0iFXN +8EX9kP6sagY61p4VHHTUTWKPrQo539uH/OvNspla2MAos/RLWFHJjWkak9eaw==
Date: Mon, 05 Feb 2024 09:47:39 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Reply-To: dcrocker@bbiw.net
Content-Language: en-US
To: ietf-dkim@ietf.org
References: <20240119192026.DEDFF810437D@ary.qy> <20240120000053.FrDLzS4U@steffen%sdaoden.eu> <3f72e0c3-d245-16f7-57b2-831bfa53efbd@taugh.com> <4F161749-91D6-4E2D-AF70-89C5F172B971@isdg.net> <64f0cfd3-9d86-4d5e-b213-d0e53972c65a@tana.it> <af70d974-b2cb-4ac3-af9f-f0461238ebbb@isdg.net> <0cb52576-67af-4248-9866-5d2e2ef1adfd@tana.it> <8EA4F7EB-CBAF-4CBA-AD3B-03ECC8B05172@isdg.net> <012291f4-5098-4e6b-b9b9-a7e1fd681138@tana.it>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
In-Reply-To: <012291f4-5098-4e6b-b9b9-a7e1fd681138@tana.it>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-CM-Analysis: v=2.4 cv=HtdwGVTS c=1 sm=1 tr=0 ts=65c11f3c a=f+oD5hTMMv8HtluUlp4ziA==:117 a=f+oD5hTMMv8HtluUlp4ziA==:17 a=-8J-CVF0aq-YtkYw:21 a=IkcTkHD0fZMA:10 a=k7Ga1wGzAAAA:8 a=aQV-GfNXFF4WGxnuBogA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=ijMaxGghyylP-n2pFjDB:22
X-CM-Envelope: MS4xfPMf1YM9Vl1X1wrmZr9pRcssMsPE0er/4LWFh8sWHwhDYMtir0O5TVWsKnPqWrSD9Gc2Yz+Ix3t/SP37MXWIU84MpbCq5fRiMF4CTCwzx+CupzLjvZzV 9W26NXY2l7Uw7FgjnlIxEnz207gu/YTVieIyBEdlNHF824N/Ju+3SuZIoKmK31td+PDnGR01x/qiqw==
X-AuthUser: dhc@dcrocker.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/58XdswUVsEaw-5LgJYffOuSlb_4>
Subject: Re: [Ietf-dkim] Headers that should not be automatically oversigned in a DKIM signature?
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2024 17:47:49 -0000

On 2/5/2024 9:43 AM, Alessandro Vesely wrote:
> It is debatable whether it is useful to display authentication 
> information to the end user.  Personally, I like to see it. 

At scale, there is no debate among UX professionals.  Its presence 
varies between useless and confusing, for typical users.

Since some miniscule portion of the user population might like to see 
it, for whatever reason, it could make sense to make it available, but 
not as a default.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social

v2.23.0 | Report a Bug | By Email