Re: dmarc damage, was gmail users read on... [bozo subtopic]

"John Levine" <johnl@taugh.com> Sat, 13 September 2014 19:14 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B421A00CA for <ietf@ietfa.amsl.com>; Sat, 13 Sep 2014 12:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.762
X-Spam-Level:
X-Spam-Status: No, score=0.762 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 zCKgjmnvwxP3 for <ietf@ietfa.amsl.com>; Sat, 13 Sep 2014 12:14:50 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0C8A1A00B8 for <ietf@ietf.org>; Sat, 13 Sep 2014 12:14:49 -0700 (PDT)
Received: (qmail 62730 invoked from network); 13 Sep 2014 19:14:49 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 13 Sep 2014 19:14:49 -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=cef.541497a8.k1409; i=johnl@user.iecc.com; bh=HKQv4eG8v1RpFmfVzObup0zyu0a4ofXrETn9It+C0M0=; b=a53yfE/AKDEco3zO0S8lLDQGFobxaLm/fbl4ag2xS7MgjJIrAF/shcat6ZQVxEPkR2HF2VjhIsaMeNeA6Uh6jECqFS60KqBYtW8iPfWP5jlttxYnRjufybdnpJynUBZRuWdz/GMOH2m9iONYf3/5Qiz6gMA1lge8bq60BxJMigAs/KPQpMDHHO/JhU3wylOkBoDzPELPsO5pDkM5gCFULokAeu2vielHu9N+e0K1eZd9S+8Qr3i7I8URHA9nR7vF
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=cef.541497a8.k1409; olt=johnl@user.iecc.com; bh=HKQv4eG8v1RpFmfVzObup0zyu0a4ofXrETn9It+C0M0=; b=CRglhVtQN4E9OMRUvdXrIeNHh33eBS0CIUMoml3nYh1AqdC8H9W8aj/ddvi+PVmRcIGCTCnPCkoyEkQ0swhTagvpnTgnLwvbkAmUejhCcMS9BUpr+h162bOr4IzQBL2w6OZIyWi5t7+GRrh2w6XG6ArW5bOfFZmD9fIH/5K1jNa6Nf6DOXcAWwIYxAAYLekw15whP+fuRqOeKTtATcAVqaLWPppOYTDICirxED+MyTD9ilrzW+AlmWog+gMaJ4fn
Date: Sat, 13 Sep 2014 19:14:26 -0000
Message-ID: <20140913191426.3310.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: dmarc damage, was gmail users read on... [bozo subtopic]
In-Reply-To: <20140912132742.GA5035@thunk.org>
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/m-lhykMowEUpQBw6x2ausITJO0o
Cc: tytso@mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Sep 2014 19:14:51 -0000

>But unfortunately, once the UI recognizes this case, would we not be
>imposing harm vis-a-vis phishing in particular?  And then DMARC Mark
>II (as it were) would have to prohibit the wrapping and require a wrap
>of a wrap, etc.

DMARC is only useful because many crooks are remarkably lazy or
stupid.  I've seen numbers showing that it blocks vast amounts of spam
with From: addresses like <security@paypal.com> which means that a lot
of crooks just uses the exact address they're attacking But it's not
effective against stuff like this, which they also use:

  From: <security@paypaI.com>
  From: security at paypal.com <boris@rbn.ru>

For that second one, remember that a lot of MUAs only show the
comment on the From: line, not the address.

While I believe that it does block considerable phish now, I also
believe it's a lot of long term pain for only short term benefits.  I
also agree that if we invent ways to circumvent DMARC issues, the bad
guys will quickly adapt unless those ways have a different, ideally
better, threat model.  See the appsawg archives and the new dmarc list
for further discussion on this point.

R's,
John