IETF Logo Mail Archive

Re: [netmod] I-D Action: draft-ietf-netmod-system-mgmt-11.txt

"Yi Yang (yiya)" <yiya@cisco.com> Thu, 06 February 2014 19:45 UTC

Return-Path: <yiya@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4E01A03CA for <netmod@ietfa.amsl.com>; Thu, 6 Feb 2014 11:45:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level:
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 BZSZ_EnLEvLJ for <netmod@ietfa.amsl.com>; Thu, 6 Feb 2014 11:45:32 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 119F41A03F3 for <netmod@ietf.org>; Thu, 6 Feb 2014 11:45:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1913; q=dns/txt; s=iport; t=1391715931; x=1392925531; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=83llOrOeAjV+y2NdCIXlKwvv5Q6cVsblpMpkVViy4+Q=; b=kQsetY9C9fGERV1clUb7+LLm87lEAJhHyep6yqWfe8XgsDMIypD/qtX8 8QIy24qNvb1I3QYELTnSEbw+AN6Zr6A5h6FRIuQGmhaQsLc7S0e+zpYwc P5cZaYnF2qohQM1Mph6rkafakt7fHBhfWVUdUbpSlSBXMT6Tf0I+uIaPG g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFANPl81KtJV2d/2dsb2JhbABQCYMMgQ++c4ENFnSCJQEBAQQ6PxACAQgOAggWAQEGEDIlAgQBDQWIBc0NF44fWwcSAQWEIAEDlEKDaZIhgy2BagcXIg
X-IronPort-AV: E=Sophos;i="4.95,795,1384300800"; d="scan'208";a="18547663"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-4.cisco.com with ESMTP; 06 Feb 2014 19:45:29 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s16JjTEx015003 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 6 Feb 2014 19:45:29 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.170]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Thu, 6 Feb 2014 13:45:29 -0600
From: "Yi Yang (yiya)" <yiya@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>, "j.schoenwaelder@jacobs-university.de" <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [netmod] I-D Action: draft-ietf-netmod-system-mgmt-11.txt
Thread-Index: AQHPFdgzGMRqtUVbW0GBh5oYMEh3NpqnL4wAgAFYt4CAABZXAIAAHaIAgAAFngCAAAsxAA==
Date: Thu, 06 Feb 2014 19:45:28 +0000
Message-ID: <CF194B57.212B0%yiya@cisco.com>
References: <20140206103915.GB49052@elstar.local> <20140206.125914.1253292680765952579.mbj@tail-f.com> <20140206134518.GD49118@elstar.local> <20140206.150524.1309921502695133115.mbj@tail-f.com>
In-Reply-To: <20140206.150524.1309921502695133115.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [64.102.95.107]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <43A5DB5DC5059A49AC87468E9A171104@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] I-D Action: draft-ietf-netmod-system-mgmt-11.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 19:45:33 -0000

Hi Martin,

One issue is for "feature local-users", as specified in section 3.5.1 and
3.5.2, it indicates support of public-key-based AND password-based
authentication for local users. But what if only public-key-based is
supported, or vice versa? How would client discover it?

Yi


On 2/6/14 9:05 AM, "Martin Bjorklund" <mbj@tail-f.com> wrote:

>Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>> On Thu, Feb 06, 2014 at 12:59:14PM +0100, Martin Bjorklund wrote:
>> > Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>> > > On Wed, Feb 05, 2014 at 07:05:30PM +0000, Yi Yang (yiya) wrote:
>> > > > I have a quick question on authentication method.
>> > > > 
>> > > > If the system supports SSH public key authentication only, but
>>not local
>> > > > user password, how user-authentication-order should be set?
>> > >  
>> > > I think this is fair question to ask. Martin and Andy, are we
>>missing
>> > > an identity for this case?
>> > 
>> > The local-users feature handles SSH keys as well, see 3.5.1.  As
>> > explained in 3.5.1, ssh public key authentication is requested by the
>> > client, so the authentication-order on the server doesn't really
>> > apply.
>> > 
>> 
>> Martin,
>> 
>> we are talking about the case where you disable password and
>> key-interactive authentication on the server side. This is actually
>> how I run the machines I am reponsible for (so I can sleep well
>> despite all the SSH login scanners out there).
>
>Ok, but it doesn't make much sense to control this with
>user-authentication-order.  The reason for this is that it is unclear
>what this means:
>
>  user-authentication-order: radius, ssh-key
>
>First radius, then ssh-key?  It doesn't make much sense.
>
>Actually, this can be achieved today if you set
>user-authentication-order to the empty list.
>
>
>/martin

v2.23.0 | Report a Bug | By Email