RE: [Isms] RE: Authentication and access control requirements

"Salowey, Joe" <jsalowey@cisco.com> Mon, 27 June 2005 00:39 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmhee-0001GA-N7; Sun, 26 Jun 2005 20:39:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmhed-0001G5-4f for isms@megatron.ietf.org; Sun, 26 Jun 2005 20:39:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28420 for <isms@ietf.org>; Sun, 26 Jun 2005 20:39:13 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dmi3e-0002ZN-W6 for isms@ietf.org; Sun, 26 Jun 2005 21:05:08 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 26 Jun 2005 17:39:05 -0700
Received: from E2K-SEA-XCH2.sea-alpha.cisco.com (e2k-sea-xch2.cisco.com [10.93.132.68]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5R0d3vM010830; Sun, 26 Jun 2005 17:39:03 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Isms] RE: Authentication and access control requirements
Date: Sun, 26 Jun 2005 17:43:18 -0700
Message-ID: <7210B31550AC934A8637D6619739CE69056DCABF@e2k-sea-xch2.sea-alpha.cisco.com>
Thread-Topic: [Isms] RE: Authentication and access control requirements
Thread-Index: AcV6VX+CeUf8APwzQCeWmia4f8Fp2AAT5BwgAAKPriA=
From: "Salowey, Joe" <jsalowey@cisco.com>
To: ietfdbh@comcast.net, Sam Hartman <hartmans-ietf@mit.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: quoted-printable
Cc: isms@ietf.org
X-BeenThere: isms@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/isms>
List-Post: <mailto:isms@lists.ietf.org>
List-Help: <mailto:isms-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=subscribe>
Sender: isms-bounces@lists.ietf.org
Errors-To: isms-bounces@lists.ietf.org

> SNMPv3 was designed to allow various types of principals to 
> be represented, in order to meet various specific 
> requirements of the operator and NMS-developer communities. I 
> am interested in understanding how the SSH concepts fit into 
> the SNMPv3 architecture.
> Does SSH support authenticating users and applications and 
> other principals, or is SSH restricted to certain types of principals?
> 

[Joe] SSH can support different types of credentials representing
different types of principals.  Typically the SSH server application is
authenticated to SSH client application using a public/private key pair,
there are other options available such as
draft-ietf-secsh-gsskeyex-09.txt which use different types of
credentials.  Once the server application has been authenticated then
SSH authentication protocol (draft-ietf-secsh-userauth-27.txt) is
executed to authenticate the client principal which typically is a user
or an application.  The SSH authentication protocol can support a wide
range of credential types.  


_______________________________________________
Isms mailing list
Isms@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/isms