Re: [dmarc-ietf] Response to a claim in draft-crocker-dmarc-author-00 security considerations

John Levine <johnl@taugh.com> Tue, 21 July 2020 02:55 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE4BD3A13E9 for <dmarc@ietfa.amsl.com>; Mon, 20 Jul 2020 19:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=IwTWUoJk; dkim=pass (1536-bit key) header.d=taugh.com header.b=tnmep5UF
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 o1zraKhCPu1B for <dmarc@ietfa.amsl.com>; Mon, 20 Jul 2020 19:55:56 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8D413A13A7 for <dmarc@ietf.org>; Mon, 20 Jul 2020 19:55:46 -0700 (PDT)
Received: (qmail 69928 invoked from network); 21 Jul 2020 02:55:45 -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=11124.5f165931.k2007; bh=ILHfs2wHZn6ZRox2EQEJKg1R+hH1cl7HzW/bTnj/ZEA=; b=IwTWUoJkCDA1RRh76lcvbtnooohVUN1AgqLGZK5uqcISFbJk0euZbe9Vwi7l2UKHZIvI0PjdRqJDOBj/N7MaeVZhVXrXsDpRemGH3VCHUfVPhb0l6lIHOyjujEmt/Q8xRgYgRudTy8hoaS9BQdXG9oAc9zXLRKKZlHS4t7gzDs4JXiQf/kZZXCgwYQpC/nok97nfeIMUo5juRVemgbjtdENGwbpuGtKd2l3UONAF+5rvogkwU+sOIrQHF0U4aMxN
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=11124.5f165931.k2007; bh=ILHfs2wHZn6ZRox2EQEJKg1R+hH1cl7HzW/bTnj/ZEA=; b=tnmep5UFs+LMLK+EfLTM9cByIK1etQOtnuwkoit0iaHBetrKWYBDc5YDY2fPV7uY4LkDkFMchMqX/lSJmMO/HuHe2n3O6lxI64z+QrYd1OSGiI+qlgKInjth9W4+VN0hI/Oj7cpK7GeWlBVJMtIXaVbyy3p3ug2o39+6pQgF/C3F4B6w9vLQxyvIEqHGYZxmWzes4PLAHXdDPulinSg/h3a924AVJJT1rrbFDwBlwIx1aZKWljiMUxUqn4vitr7s
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 21 Jul 2020 02:55:45 -0000
Received: by ary.qy (Postfix, from userid 501) id 27E961D58026; Mon, 20 Jul 2020 22:55:45 -0400 (EDT)
Date: Mon, 20 Jul 2020 22:27:15 -0400
Message-Id: <20200721022717.A51D31D57B7C@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: jesse.thompson@wisc.edu
In-Reply-To: <d8bab034-7539-fbb4-faa0-daf6aa51e087@wisc.edu>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ayjKXxfTRBCCGJlpgVf_qUTUG3o>
Subject: Re: [dmarc-ietf] Response to a claim in draft-crocker-dmarc-author-00 security considerations
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2020 02:56:04 -0000

In article <d8bab034-7539-fbb4-faa0-daf6aa51e087@wisc.edu> you write:
>Why should the rest of end-users suffer?  (some might say)
>
>Granted, we are a university.  Maybe these are just faculty being hyper-sensitive to how
>their messages are appearing to their peers/students.  But isn't that enough evidence that
>end-users *are* relevant?  With time, maybe we can change these end-user expectations, and
>From rewriting will be the new reality that people will accept.

I don't think the claim is that users don't see anything, it's that
they're no good at using what they see to make security decisions,
something that has more to do with mental models and metaphors between
what's on the screen and reality.

>I think that draft-kucherawy-dkim-transform-02 is getting at what I was originally thinking. 
>In my opinion, MLMs will *always* need to munge, because they will never know if an arbitrary
>receiver will trust their non-munged mail.  Giving the receivers a way to un-munge (if they
>can and/or want and/or trust) would be a productive path forward out of this situation.

We already have a couple of ways to do reversible message munging,
starting with MIME message wrapping. In principle it works fine, in
practice it's awful because MUAs don't show wrapped messages
consistently and often in ways that are painful, e.g., you can see the
original author address but there's no button you can push to respond
to it.

Unwrapping a MIME attachment is a lot easier than the proposed DKIM
unmunging but I doubt either is going to show up in MTAs any time
soon.  Perhaps you could do it in the mail gateway.

R's,
John