IETF Logo Mail Archive

Re: [saag] Using ED25519 in SSHFP Resource Records - draft-moonesamy-sshfp-ed25519-00

Yoav Nir <ynir@checkpoint.com> Sun, 23 February 2014 11:53 UTC

Return-Path: <ynir@checkpoint.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 19A241A007F for <saag@ietfa.amsl.com>; Sun, 23 Feb 2014 03:53:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.449
X-Spam-Level:
X-Spam-Status: No, score=-7.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 e1VNH-FqVKOK for <saag@ietfa.amsl.com>; Sun, 23 Feb 2014 03:53:33 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 593521A007C for <saag@ietf.org>; Sun, 23 Feb 2014 03:53:33 -0800 (PST)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id s1NBqvvG027924; Sun, 23 Feb 2014 13:53:01 +0200
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.228]) by DAG-EX10.ad.checkpoint.com ([169.254.3.228]) with mapi id 14.03.0123.003; Sun, 23 Feb 2014 13:52:57 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Thread-Topic: [saag] Using ED25519 in SSHFP Resource Records - draft-moonesamy-sshfp-ed25519-00
Thread-Index: AQHPId7rWAu668QniUCvg4caHxc2CprCtlOA
Date: Sun, 23 Feb 2014 11:52:56 +0000
Message-ID: <23AC0B40-66B5-468C-B96D-17B52F1F42A4@checkpoint.com>
References: <6.2.5.6.2.20140204112023.0aec4c90@elandsys.com>
In-Reply-To: <6.2.5.6.2.20140204112023.0aec4c90@elandsys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.24.46]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <33FF800B7C24434E980326A1BD1EACF0@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/saag/Wi5aEvJIw7_rf0dhXuHE34xA0mM
Cc: "<saag@ietf.org>" <saag@ietf.org>
Subject: Re: [saag] Using ED25519 in SSHFP Resource Records - draft-moonesamy-sshfp-ed25519-00
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: <http://www.ietf.org/mail-archive/web/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: Sun, 23 Feb 2014 11:53:36 -0000

Hi, SM

The draft looks fine, but I have to ask, why do you define both ED25519-with-SHA256 and ED25519-with-SHA1 ?

I can't think of somebody writing an implementation today that would have ED25519 but not have SHA256, so I think you might as well require SHA256 unless this is something you can't do per RFC 4255.

Yoav

On Feb 4, 2014, at 9:20 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
> 
> As a FYI:
> 
>   The Ed25519 signature algorithm has recently been implemented in
>   OpenSSH.  This document updates the IANA "SSHFP RR Types for public
>   key algorithms" registry by adding an algorithm number for Ed25519.
> 
> http://tools.ietf.org/html/draft-moonesamy-sshfp-ed25519-00
> 
> Regards,
> S. Moonesamy
> 
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag
> 
> Email secured by Check Point

v2.23.0 | Report a Bug | By Email