IETF Logo Mail Archive

Re: [saag] AD review of draft-iab-crypto-alg-agility-06

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Mon, 24 August 2015 21:38 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A3601A8A0E for <saag@ietfa.amsl.com>; Mon, 24 Aug 2015 14:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 PRCVOANprwpi for <saag@ietfa.amsl.com>; Mon, 24 Aug 2015 14:38:48 -0700 (PDT)
Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B80621A897B for <saag@ietf.org>; Mon, 24 Aug 2015 14:38:48 -0700 (PDT)
Received: by qgeg42 with SMTP id g42so95780614qge.1 for <saag@ietf.org>; Mon, 24 Aug 2015 14:38:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=u1MrGZ/j5cIg7dV2e2kkWPDLov4IB/nL8eFam5NJopY=; b=Eem357mWzU4YPtLX6CjWbBQ+0Ey6dCHNN17pfCNh8qGWSQO/hqqFkCF/hrwQOlI3KM VDwLpp8OKtT4dQiYUx5QA7784ICcheDjPk6Tgf/uKqpODQ+pvktagE7l1Lw9GhEmubk1 J1NiJErrfuaHx14V1bCHhlutRh9Uj6X1jwMC77c13MCAyi+LxS3vf1sr5thhUGvIT9R9 6h17KpTAKAj8y/c+jRXWNqc6ajm4UMjRYcx50bzZ+lwOQyIkNOl/D5iEMV5lXYutzu6S Y8+E3I6CAkmvdjs3TvBicQazYOQnaZTDO0YLQhaYGX4XFCE5F4F4A+70VRHeWxgFsuyJ DtTw==
X-Received: by 10.140.231.208 with SMTP id b199mr62405664qhc.87.1440452327815; Mon, 24 Aug 2015 14:38:47 -0700 (PDT)
Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by smtp.gmail.com with ESMTPSA id s64sm10386794qgs.33.2015.08.24.14.38.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Aug 2015 14:38:47 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <619ffebb05ba4e2a9af03a6dcc768d6e@ustx2ex-dag1mb2.msg.corp.akamai.com>
Date: Mon, 24 Aug 2015 17:38:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <846AD897-C38F-4528-849D-B98B2D87798B@gmail.com>
References: <55A938F1.9090404@cs.tcd.ie> <CD936D80-BEA2-4918-828C-E3A392761EC5@gmail.com> <20150727194020.GD15860@localhost> <55B6D36C.70105@iang.org> <20150728013020.GO4347@mournblade.imrryr.org> <DM2PR0301MB0655CF099FA7C56E9B9D24A9A88D0@DM2PR0301MB0655.namprd03.prod.outlook.com> <20150728053035.GR4347@mournblade.imrryr.org> <CAHbuEH7B3_G9vAhw=U2tuz-Uh8mKMUfL6s=H+BOG96FDZaACig@mail.gmail.com> <20150824212907.GN9021@mournblade.imrryr.org> <619ffebb05ba4e2a9af03a6dcc768d6e@ustx2ex-dag1mb2.msg.corp.akamai.com>
To: "Salz, Rich" <rsalz@akamai.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/QYgDLRWMXCjYmznvXPb3dIy3a9c>
Cc: "saag@ietf.org" <saag@ietf.org>
Subject: Re: [saag] AD review of draft-iab-crypto-alg-agility-06
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2015 21:38:50 -0000


Sent from my iPhone

On Aug 24, 2015, at 5:32 PM, Salz, Rich <rsalz@akamai.com> wrote:

>> With *legacy* protocols, when negotiating unauthenticated opportunistic
>> encryption, it is important to not exclude recently obsoleted algorithms that
>> are still needed for interoperability lest failing to offer them cause
>> communications failure or needless use of cleartext.
> 
> And here, I think, is the rub.
> 
> SMTP is a legacy protocol.  Is opportunistically-encrypted SMTP a legacy protocol?  How long has it been in common use?  How old is the crypto that these deployed systems have access to?
> 
I agree this is the problem/poster child for this discussion.  I'd rather phrase it that in some cases, deprecated crypto will be used when libraries/software can't be updated rather than saying it's okay because it falls into OS.  But this may just be me.

Thanks,
Kathleen 

> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag

v2.23.0 | Report a Bug | By Email