Re: [OPSEC] draft-bhatia-manral-igp-crypto-requirements
Glen Kent <glen.kent@gmail.com> Tue, 24 February 2009 17:04 UTC
Return-Path: <glen.kent@gmail.com>
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61E123A6A89 for <opsec@core3.amsl.com>; Tue, 24 Feb 2009 09:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0lLopDRp1XN8 for <opsec@core3.amsl.com>; Tue, 24 Feb 2009 09:04:11 -0800 (PST)
Received: from mail-bw0-f161.google.com (mail-bw0-f161.google.com [209.85.218.161]) by core3.amsl.com (Postfix) with ESMTP id 304713A6B39 for <opsec@ietf.org>; Tue, 24 Feb 2009 09:04:11 -0800 (PST)
Received: by bwz5 with SMTP id 5so5959173bwz.13 for <opsec@ietf.org>; Tue, 24 Feb 2009 09:04:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=weboz/dery0d8SINfDwbDxY5KjMm7KH3xbzjvq+j0bw=; b=X2i911Uqm7GrmoeCGdhgAJznI/HYhRXn22+1BkZNae97lNycwlNrVp0kSbUZUkWwvl bJumQiLfddGsundfz+s6nHzs0ecyIAH80cNLA+lzkx4SRPdyprYC4pZs4jOT0SXYUk/e qaRKFSBJYua4SWi+8FYjTiOZdwLUincxtpQAk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MhxhhE+y1/HvT7OkjdKH04pwYbvhxHHAwAP+jmgPzF87MmR0UpgV/hNDcwn5011aVP 7Ux77kd9/lfjuOkbnr8ir3qX5G2DMdPABVBrgWuxnIBGnpyRyv2XXxXdaGB0OUlaPWMR w8yjTW9tTr9Ju5LxoG2jX/7DUMV/ACqGpV/Zo=
MIME-Version: 1.0
Received: by 10.223.124.147 with SMTP id u19mr2628far.28.1235495061918; Tue, 24 Feb 2009 09:04:21 -0800 (PST)
In-Reply-To: <77ead0ec0902232009s260cee0dn4f81390ddf698e1c@mail.gmail.com>
References: <77ead0ec0902232009s260cee0dn4f81390ddf698e1c@mail.gmail.com>
Date: Tue, 24 Feb 2009 22:34:21 +0530
Message-ID: <92c950310902240904y31537b3cn1837b4a78ba4a40b@mail.gmail.com>
From: Glen Kent <glen.kent@gmail.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: opsec wg mailing list <opsec@ietf.org>
Subject: Re: [OPSEC] draft-bhatia-manral-igp-crypto-requirements
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 17:04:12 -0000
So was there any ambiguity in recommending HMAC-SHA1 over other available options ever? I re-read the document, found it extremely simple, the recommendations look right, found it just to be what OPSEC must own up. Glen On Tue, Feb 24, 2009 at 9:39 AM, Vishwas Manral <vishwas.ietf@gmail.com> wrote: > Hi folks, > > We now have got some clear guidance regarding this document from the > Security AD's regarding the cryptographic algorithms (Joel has been > privy to those mails). The guidance seems to second what Hugo and > other cryptographers have been stating all along. The crux of what has > been said is: > > MD5 should not be used for crypto purposes. SHA-1 though stronger is > also vulnerable. HMAC-MD5 though not yet vulnerable looks highly > suspect and should not be reccomended. HMAC-SHA-1 for now looks ok and > can be reccomended. Goinf forward we should try to reccomend the SHA-2 > family of protocols. > > With these clear guidances matching what we have in our documents, I > would like to ask the working group to look into this document > further. We can then look at getting this as a WG document. > > Thanks, > Vishwas > _______________________________________________ > OPSEC mailing list > OPSEC@ietf.org > https://www.ietf.org/mailman/listinfo/opsec >
- [OPSEC] draft-bhatia-manral-igp-crypto-requiremen… Vishwas Manral
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Glen Kent
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Vishwas Manral
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Joel Jaeggli
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Vishwas Manral
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Joel Jaeggli
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Bhatia, Manav (Manav)
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… John Smith
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Pasi.Eronen
- Re: [OPSEC] draft-bhatia-manral-igp-crypto-requir… Vishwas Manral