IETF Logo Mail Archive

Re: [dane] Comments on draft-ietf-dane-smime-04

Stephen Kent <kent@bbn.com> Fri, 14 February 2014 16:07 UTC

Return-Path: <kent@bbn.com>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C9441A02D6 for <dane@ietfa.amsl.com>; Fri, 14 Feb 2014 08:07:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level:
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
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 r-3aTuPpqaLz for <dane@ietfa.amsl.com>; Fri, 14 Feb 2014 08:07:49 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id B100A1A0284 for <dane@ietf.org>; Fri, 14 Feb 2014 08:07:45 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15]:50928 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1WELIl-000K28-OW for dane@ietf.org; Fri, 14 Feb 2014 11:07:43 -0500
Message-ID: <52FE3F4D.6020100@bbn.com>
Date: Fri, 14 Feb 2014 11:07:41 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dane@ietf.org
References: <07ba01cf23b9$4b4e0540$e1ea0fc0$@augustcellars.com> <D84E4FB1-8B9F-4C16-80F6-A307B2E0B0AD@verisign.com> <m3ob2a396e.fsf@carbon.jhcloos.org>
In-Reply-To: <m3ob2a396e.fsf@carbon.jhcloos.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dane/dQj-LzVEzU2rFDHYag0q9k5u_oY
Subject: Re: [dane] Comments on draft-ietf-dane-smime-04
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dane/>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 16:07:51 -0000

James,

>>>>>> "OE" == Osterweil, Eric <eosterweil@verisign.com> writes:
> OE> With PGP, I can use a key with a diff email than the account from
> OE> which I send it (for ex, I can use my spam account and rely on my
> OE> full name and friends who know me to make the logical leap), do we
> OE> all want DANE to outlaw this for S/MIME?
>
> Absolutely not.
>
> There is no value in forcing the sending email address to match the info
> in any signature over the message (or over any part of the message).
>
> (With emphasis on /forcing/.)
 From an OE perspective, I see your point. Form a general security 
perspective,
I disagree. Folks receiving a signed message tend to assume that the "from"
field has been checked against the Subject or SAN in the signer's cert. It's
a reasonable expectation. When that reasonable assumption is not true, users
are surprised, and surprise is a bad outcome wrt security :-).

Steve

v2.23.0 | Report a Bug | By Email