Re: [ietf-822] A permission to re-sign header

"John Levine" <johnl@taugh.com> Sun, 20 April 2014 01:35 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 956B91A0096 for <ietf-822@ietfa.amsl.com>; Sat, 19 Apr 2014 18:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level:
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMVBNVT3GpXj for <ietf-822@ietfa.amsl.com>; Sat, 19 Apr 2014 18:35:29 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 603AE1A0084 for <ietf-822@ietf.org>; Sat, 19 Apr 2014 18:35:29 -0700 (PDT)
Received: (qmail 83627 invoked from network); 20 Apr 2014 01:35:24 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 20 Apr 2014 01:35:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=de31.5353245c.k1404; i=johnl@user.iecc.com; bh=BxAEh1aU4uPLP1zi5Q1iyweaRb7qx0cGuVhxqPJ55AE=; b=cyDSQSxprVMJoYUObvu+9c1e7CzGb7gT5kRLF0h1TAozQFH5deTxiLikDSHsksBrpI3bve6luJFwS4BPd0pqHAtpU09kFzFjq5DK6DWMzCWlQCNe+lbHh2qs039Qoc3vCweIKZb+NeKlsw5AZ6Zyxhk/OZi4D7DukAaodEm3ZKJDnvx9Xy+jG2q4ppEFNFqBIQgvoM0a5kqlSoMbijP0k4eir9UH1/MGcXgWN+zWg+bnA74G58GjSivl2htbXbXo
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=de31.5353245c.k1404; olt=johnl@user.iecc.com; bh=BxAEh1aU4uPLP1zi5Q1iyweaRb7qx0cGuVhxqPJ55AE=; b=j2iQMX+l9plUbuZKkJ4F2mqN+sca3t9A2u2LTLiG7/ebpbCUYRnkQWa7Mg8S2gPzymY7m9jneJo05st+klwe5Gny4jpWheXgH3FBYaOIEcfRtMdeZVsZviK7Vvm89AxfFhj6B/dS4UvUfWR3wt7C8wOs1LoKxL6YCySvDzqthqAzF6l8ZDlb8N8VlUwXK9PmoLYUXnwFVChbtym+A2/YSF17iXlxn75gri1+PvZXoRtUNQgAZ0biJcJH6YUn0ZpE
Date: Sun, 20 Apr 2014 01:35:00 -0000
Message-ID: <20140420013500.56880.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf-822@ietf.org
In-Reply-To: <53530E05.1010006@meetinghouse.net>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/1V5T6wGg26AxcVwbe9WRXgHb6UM
Cc: mfidelman@meetinghouse.net
Subject: Re: [ietf-822] A permission to re-sign header
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 01:35:33 -0000

>Is that not a critical goal?  As a sender, I want to make sure that my 
>message gets through intact (authentication and integrity).

The copy of your message that showed up here was mutated by the
mailing list by adding a subject tag and a footer.  That is presumably
not a problem, since you've sent a bazillion messages to IETF lists.

Every previous attempt to describe mechanically what is a good
mutation vs. a bad one has been a complete failure.  The best we can
do is to try to verify that the mutations were done by someone you
trust.

Even that fails to describe the situations where a message was sent
with your approval, but not by a sender that happens to have your
signing key or use one of your SPF IP addresses.

R's,
John