Re: [Curdle] AD Review: draft-ietf-curdle-ssh-ext-info-00.txt

Eric Rescorla <ekr@rtfm.com> Mon, 19 June 2017 17:13 UTC

Return-Path: <ekr@rtfm.com>
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 CAA6C131625 for <curdle@ietfa.amsl.com>; Mon, 19 Jun 2017 10:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 M0wyQ7taDjYI for <curdle@ietfa.amsl.com>; Mon, 19 Jun 2017 10:13:20 -0700 (PDT)
Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (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 BCE7D131614 for <curdle@ietf.org>; Mon, 19 Jun 2017 10:13:01 -0700 (PDT)
Received: by mail-yb0-x22d.google.com with SMTP id 84so30000869ybe.0 for <curdle@ietf.org>; Mon, 19 Jun 2017 10:13:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gFYP/w4GM7HGeQMFhKz1baN5cvKcNnVGKxmEoDrnnco=; b=uXNrfcJGnsAmQp9evF+J7BlyjUpZVptQp8TBvfY9eK5ceDtgmUGJLFkSwfp2MWtrsw dDpswMcViSrBgIT3FceQU0K36vSb2kK2cNpGKYP4b+2o1E20ZAw2vX019mkVF+h2zrWe GlEQz/8EKt0Xu4ZDqcFLlOW85wAmWoqhX2QXGjLMmjpqKqDSPTBF3/23HdT565BEaoo7 4Hv/ZWvlZ/5NkIBAEcAxtlLg4VA9JHV57KJhGUaJmRahaWty0dF1PDjas1h8XVjjxqI5 OBLVgVb29U6IdxQAZenuVtmXVFVzjq8uweXPo3JLAS3+6ZO21xCIVm6wNyHyR4zf6/BI uClg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gFYP/w4GM7HGeQMFhKz1baN5cvKcNnVGKxmEoDrnnco=; b=Lmcp1w2O5GESuC0e0Z6ibmsj5U/l6lUE6/4JwX9YGGB3hlJ5+fDOu+OL8CTSr/EgwA dD1DYL3Bwjz4JfksBsGhXGKJyQZFBgXIA2SkU04qvhBBHKTaF2mdDOy9ipi4kdWhSs35 2JkU0AzHy2QMl2WRxlasJWL08tiNYPo1K+6kibmkjwMhayTKTM1A2wQTiPguitT60nWP JaqfOx3FUOnBJtUgeXWkQKr/RuDZZf4DUUbQhTuHVk+X8LGdG5pGTuU0yFOSknoqXab5 vLEEeS3WhNewfS/W2v58pDRApR45zvtkAAUxkfedjLf9sNcG4wzpcml9pY4Atp9vnJ8o dmcg==
X-Gm-Message-State: AKS2vOxe3i0bqguAZGHUkSi+V2o9YjBCYdDv0/F6xKlMmqaSvaCTpO+i RqUrMg1npaKt5beM7vjyB2HmRMFSe0F6
X-Received: by 10.37.162.104 with SMTP id b95mr19541919ybi.29.1497892380879; Mon, 19 Jun 2017 10:13:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.215.144 with HTTP; Mon, 19 Jun 2017 10:12:20 -0700 (PDT)
In-Reply-To: <CADPMZDD8PEV7MzF2ObHk5pHGE4v+VXSj2HcKnhLr4bQNuvrfVg@mail.gmail.com>
References: <CABcZeBPHNrDh4pNUMEB0UWw+uH13g4zUDYLrwirz8jCaoh8XLA@mail.gmail.com> <CADPMZDD8PEV7MzF2ObHk5pHGE4v+VXSj2HcKnhLr4bQNuvrfVg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 19 Jun 2017 10:12:20 -0700
Message-ID: <CABcZeBPfK4HELh5RHP5txRsfcA2m0ZcMCZzKZKB5wxPW+PjxOw@mail.gmail.com>
To: denis bider <denisbider.ietf@gmail.com>
Cc: curdle <curdle@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c19fcf847070e0552533f8d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/Q1fFq360c9PT4wl4mqVi9o_-auY>
Subject: Re: [Curdle] AD Review: draft-ietf-curdle-ssh-ext-info-00.txt
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: Mon, 19 Jun 2017 17:13:23 -0000

Thanks. This all looks fine.

On Mon, Jun 19, 2017 at 9:13 AM, denis bider <denisbider.ietf@gmail.com>
wrote:

> > Can you explain what "neutral" means?
>
> Rephrased as:
>
> "The indicator names inserted by the client and server are different to ensure
> these names will not produce a match, and therefore not affect the
> algorithm chosen in key exchange algorithm negotiation."
>
>
> > Can a server send ext-info-s if it did not receive ext-info-c?
>
> Certainly. RFC 4253 makes no suggestions that either client or server
> should wait for the other with their KEXINIT packet. The server is free to
> send KEXINIT before receiving anything from the client.
>
> I have made this clearer by elaborating Section 2.2.
>
>
> > You need a citation for "elevated."
>
> I have added the following paragraph:
>
> "The terms "elevation" and "elevated" refer to an operating system mechanism
> where an administrator user's logon session is associated with two
> security contexts: one limited, and one with administrative rights. To
> "elevate" such a session is to activate the security context with full
> administrative rights. For more information about this mechanism on
> Windows, see also [WINADMIN] and [WINTOKEN]."
>
> The informative references are:
>
> WINADMIN:
> https://blogs.msdn.microsoft.com/winsdk/2013/03/22/how-to-
> launch-a-process-as-a-full-administrator-when-uac-is-enabled/
>
> WINTOKEN:
> https://msdn.microsoft.com/en-us/library/windows/desktop/bb530718.aspx
>
>
> denis
>
>
>
> On Sat, Jun 17, 2017 at 1:37 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>
>>
>> S 2.1.
>>   The indicator names inserted by the client and server are different to
>>   ensure that these names will not produce a match, and will be neutral
>>   with respect to key exchange algorithm negotiation.
>>
>> Can you explain what "neutral" means?
>>
>>
>> S 2.2.
>> If a client or server offers "ext-info-c" or "ext-info-s"
>>   respectively, it must be prepared to accept a SSH_MSG_EXT_INFO message
>>   from the peer.
>>
>> Can a server send ext-info-s if it did not receive ext-info-c?
>>
>>
>> S 3.4.
>>   A client sends "y" to indicate its preference that the session should
>>   be elevated; "n" to not be elevated; and "d" for the server to use its
>>   default behavior. If a client does not send the "elevation" extension,
>>   the server SHOULD act as if "d" was sent.
>>
>> You need a citation for "elevated."
>>
>>
>>
>> _______________________________________________
>> Curdle mailing list
>> Curdle@ietf.org
>> https://www.ietf.org/mailman/listinfo/curdle
>>
>>
>