IETF Logo Mail Archive

Re: [secdir] [taugh.com-standards] Security review of draft-levine-herkula-oneclick-05

"John R. Levine" <johnl@iecc.com> Sun, 18 September 2016 16:18 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172AB12B12C for <secdir@ietfa.amsl.com>; Sun, 18 Sep 2016 09:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com
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 CELUYiFYHpdr for <secdir@ietfa.amsl.com>; Sun, 18 Sep 2016 09:18:39 -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-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34FB2127A91 for <secdir@ietf.org>; Sun, 18 Sep 2016 09:18:39 -0700 (PDT)
Received: (qmail 8090 invoked from network); 18 Sep 2016 16:18:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1f98.57debe5c.k1609; bh=MecP/Qdw9HfjvTw//wSYqCyJbXMI48pmMSajqtlmTCM=; b=jVEjMd/VAmuIQXIXpzLQNYOaliDPfcQVJ/fg0DI/QhURuPy4vHs+nQDUFRDKrFDul8wY3dMx5/0dDSSjCkVnzea1P7qrG+ys3hPtKlAYe4RKoQi1+XE2fkhz6wU2RotQtLEH6K2cTvk7QvcO7EdTOfhVeQ23CupjzA6/45yxPhug4UX0uzDFFI/E6g23mIYt4007o2LjFwxeoJDd58Gjq0IUR5ze2bEom9JB46xESywAFpsrtdo6xfg5GwUF8zYR
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 18 Sep 2016 16:18:36 -0000
Date: Sun, 18 Sep 2016 12:18:37 -0400
Message-ID: <alpine.OSX.2.11.1609181216340.4398@ary.lan>
From: "John R. Levine" <johnl@iecc.com>
To: Ben Laurie <benl@google.com>
In-Reply-To: <CABrd9SQt9K+78WOm9aO_fObrvThKCVKyXAVF6WVmm=bN8c9bvw@mail.gmail.com>
References: <CABrd9SQt9K+78WOm9aO_fObrvThKCVKyXAVF6WVmm=bN8c9bvw@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/7RqNa3rca7hf5GlANxIeiDBsYQg>
Cc: draft-levine-herkula-oneclick.all@ietf.org, Paul Kincaid-Smith <paulkincaidsmith@gmail.com>, The IESG <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [secdir] [taugh.com-standards] Security review of draft-levine-herkula-oneclick-05
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Sep 2016 16:18:41 -0000

> "The URI and POST arguments SHOULD include a hard to forge component
> such as an HMAC (RFC 2104) of the other components, using a secret
> key, in addition to or instead of the plain-text names of the list and
> the subscriber."
>
> Although its kinda obvious, you should probably also say that the
> server SHOULD verify this HMAC.

It couldn't hurt, I'll put it into the -06.

> Finally, since the URI argument is the subject of an existing RFC
> (2369) that RFC should probably be updated to include this advice.

I don't think that's right.  The usual way to verify a 2369 unsubscribe is 
to ask for confirmation, either in a web page if the URI is an http or 
https, or by writing back if it's mailto:.  That doesn't change for the 
current GET syntax of 2369.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email