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

Derek Atkins <derek@ihtfp.com> Thu, 27 August 2015 13:35 UTC

Return-Path: <derek@ihtfp.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 34D971B3A8F for <saag@ietfa.amsl.com>; Thu, 27 Aug 2015 06:35:10 -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] 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 LhZxgbknzoSo for <saag@ietfa.amsl.com>; Thu, 27 Aug 2015 06:35:08 -0700 (PDT)
Received: from mail2.ihtfp.org (mail2.ihtfp.org [IPv6:2001:4830:143:1::3a11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47CDE1B3A88 for <saag@ietf.org>; Thu, 27 Aug 2015 06:35:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 0F38FE2035; Thu, 27 Aug 2015 09:35:07 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 23151-10; Thu, 27 Aug 2015 09:35:05 -0400 (EDT)
Received: from securerf.ihtfp.org (unknown [IPv6:fe80::ea2a:eaff:fe7d:235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mocana.ihtfp.org", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail2.ihtfp.org (Postfix) with ESMTPS id D8141E2034; Thu, 27 Aug 2015 09:35:04 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1440682504; bh=C2wqTD0inMtchyX5oceB0SEz1haxEwPjxOKv5tVVJqc=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=aQMdaihngEwlImcI/LdsVDclD/MvZF1+YuR+ws8o6zeZi/H3Lmgs4SLVLEX3VKhCs +dEnzsabiGHCmS2DPjkbWzf9Ll9r6+oR76STDr2K2ZN37MHkZwjW5IKRq7fuJEsAXe gfbcvVWnOips9oQ/xnUZzFJMfvkb6gyMr1TAMfjg=
Received: (from warlord@localhost) by securerf.ihtfp.org (8.14.8/8.14.8/Submit) id t7RDZ4Vk019622; Thu, 27 Aug 2015 09:35:04 -0400
From: Derek Atkins <derek@ihtfp.com>
To: Martin Thomson <martin.thomson@gmail.com>
References: <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> <20150824215037.GO9021@mournblade.imrryr.org> <9A043F3CF02CD34C8E74AC1594475C73F4AE62A1@uxcn10-5.UoA.auckland.ac.nz> <20150825134333.GX9021@mournblade.imrryr.org> <6b5167f3d0684a8a91caa6d37dec65e3@ustx2ex-dag1mb2.msg.corp.akamai.com> <20150825160627.GH9021@mournblade.imrryr.org> <CAHbuEH5r5s8ofChzt0_Rd8dxKqf8KXLDteYw8RSBX43nyFrN+A@mail.gmail.com> <2E7E9F38-DA68-4933-AD67-CF2A8E51B4F7@dukhovni.org> <7CEEF500-4530-4245-A3DC-C7D1ACB754B6@gmail.com> <CABkgnnVRdt65Vo0ReTbxpD8DqFErSTgi33qPrU5YNuy9PQBCzg@mail.gmail.com>
Date: Thu, 27 Aug 2015 09:35:04 -0400
In-Reply-To: <CABkgnnVRdt65Vo0ReTbxpD8DqFErSTgi33qPrU5YNuy9PQBCzg@mail.gmail.com> (Martin Thomson's message of "Tue, 25 Aug 2015 11:13:44 -0700")
Message-ID: <sjm7fogkg6v.fsf@securerf.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/6O4RMAnPRxpheNkrqjiKb0FBv2s>
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: Thu, 27 Aug 2015 13:35:10 -0000

Martin Thomson <martin.thomson@gmail.com>; writes:

> Since Kathleen asks so nicely, I'd like to register my disagreement
> with Victor on this point.
>
> There are compatibility reasons *today* that exist as a result of
> having to interoperate with old software that was built or deployed
> without due regard to security updates or continuous maintenance.
>
> However, if we expect software to be updated in order to get
> opportunistic security, then I don't think it unreasonable to also
> expect it to be maintained on an ongoing basis.  A sudden once-off
> isn't going to cut it if we want to prepare for the eventuality where
> one of the current ciphers turns out to be irredeemably busted.
>
> If you accept that software that is updated once can be continuously
> maintained thereafter, then it's not a stretch to conclude that
> deploying good ciphers is equally feasible.

I disagree.  Most IT players I know set something up and basically don't
touch it unless something breaks.  They don't regularly update stuff
unless they have to (and I'll hand-wave at what indicates they "have to"
-- some people are definitely more proactive and a CVE might be enough
to trigger the update).  The fact that we're still seeing 12-year-old
software in deployment (Exchange 2003) seems to back up my point that
once stuff is deployed and "worked" it tends to be left alone.

My personal feeling that "some" crypto is better than "no"
crypto.... MOST of the time.  I think all of us would argue that "rot13"
is probably *not* better than no crypto.  So where do we draw the line
as to what's a step forward and what's a false sense of security?  Do we
draw the line at rot13?  RC4-40?  RC4-128?  DES?  3DES?

And once we agree that we need to have that line, does that line need to
move over time?  And how do we move that line?

Is there some way we can pop errors up the stack in a way that the end
users can be notified that something is wrong?  Just returning a "45x
Cipher Too Weak" SMTP error code isn't going to help, because I know of
nobody that actively monitors those logs sufficiently to even NOTICE
that they get that message.  Often you'll only start to check the logs
once you notice mail isn't flowing at all, and even then you'll only
really know for outbound email, not inbound email!

-derek
-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant