Re: [Curdle] draft-ietf-curdle-ssh-kex-sha2 and diffie-hellman-group1-sha1 (1024-bit DH)

Damien Miller <djm@mindrot.org> Fri, 21 July 2017 04:15 UTC

Return-Path: <djm@mindrot.org>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89BA3126C2F for <curdle@ietfa.amsl.com>; Thu, 20 Jul 2017 21:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NCQfiFgzSqPv for <curdle@ietfa.amsl.com>; Thu, 20 Jul 2017 21:15:09 -0700 (PDT)
Received: from newmailhub.uq.edu.au (mailhub1.soe.uq.edu.au [130.102.132.208]) by ietfa.amsl.com (Postfix) with ESMTP id 06E4512441E for <curdle@ietf.org>; Thu, 20 Jul 2017 21:15:08 -0700 (PDT)
Received: from smtp2.soe.uq.edu.au (smtp2.soe.uq.edu.au [10.138.113.41]) by newmailhub.uq.edu.au (8.14.5/8.14.5) with ESMTP id v6L4F4FX004854; Fri, 21 Jul 2017 14:15:04 +1000
Received: from mailhub.eait.uq.edu.au (hazel.eait.uq.edu.au [130.102.60.17]) by smtp2.soe.uq.edu.au (8.14.5/8.14.5) with ESMTP id v6L4F4S0038490 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 21 Jul 2017 14:15:04 +1000
Received: from haru.mindrot.org (haru.mindrot.org [130.102.96.5]) by mailhub.eait.uq.edu.au (8.15.1/8.15.1) with ESMTP id v6L4F2mN011131; Fri, 21 Jul 2017 14:15:03 +1000 (AEST)
Received: from localhost (localhost [127.0.0.1]) by haru.mindrot.org (OpenSMTPD) with ESMTP id 34be3c8a; Fri, 21 Jul 2017 14:14:27 +1000 (AEST)
Date: Fri, 21 Jul 2017 14:14:27 +1000
From: Damien Miller <djm@mindrot.org>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
cc: "curdle@ietf.org" <curdle@ietf.org>, "Mark D. Baushke" <mdb@juniper.net>
In-Reply-To: <1500607284832.92144@cs.auckland.ac.nz>
Message-ID: <alpine.BSO.2.20.1707211413070.14080@haru.mindrot.org>
References: <22892.35863.542104.942153@fireball.acr.fi> <82005.1500305248@eng-mail01.juniper.net>, <alpine.BSO.2.20.1707201053511.14080@haru.mindrot.org> <1500519070842.37117@cs.auckland.ac.nz>, <alpine.BSO.2.20.1707201345030.14080@haru.mindrot.org> <1500524115986.58764@cs.auckland.ac.nz>, <alpine.BSO.2.20.1707211053360.14080@haru.mindrot.org> <1500607284832.92144@cs.auckland.ac.nz>
User-Agent: Alpine 2.20 (BSO 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.73 on UQ Mailhub
X-Scanned-By: MIMEDefang 2.75 on 130.102.60.17
X-UQ-FilterTime: 1500610504
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/Qx71vtJDH_f7qkoJCNB1ZxS83LE>
Subject: Re: [Curdle] draft-ietf-curdle-ssh-kex-sha2 and diffie-hellman-group1-sha1 (1024-bit DH)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 04:15:12 -0000

On Fri, 20 Jul 2017, Peter Gutmann wrote:

> Damien Miller <djm@mindrot.org> writes:
> 
> >On Thu, 20 Jul 2017, Peter Gutmann wrote:
> >
> >> That assumes OpenSSH is the client.  When I run into it it's always the
> >> server, so there's no error message or other information available.
> >
> >Isn't it the client's job to generate a useful error then?
> 
> What error message could the client display?  All it knows is that the remote
> server claims to be OpenSSH, and it shut down the connection after getting the
> client hello.  At which point you're back to trial-and-error with the server
> admin to try and get them to figure out a config that works.

The server doesn't shut down the connection before sending its own KEXINIT
that includes the set of supported algorithms.

-d