draft-ietf-secsh-publickey-subsystem-05.txt   draft-ietf-secsh-publickey-subsystem-06.txt 
Secure Shell Working Group J. Galbraith Secure Shell Working Group J. Galbraith
Internet-Draft J. Van Dyke Internet-Draft J. Van Dyke
Expires: March 25, 2006 B. McClure Intended status: Informational B. McClure
VanDyke Software Expires: February 1, 2007 VanDyke Software
J. Bright J. Bright
Silicon Circus Silicon Circus
September 21, 2005 July 31, 2006
Secure Shell Public-Key Subsystem Secure Shell Public-Key Subsystem
draft-ietf-secsh-publickey-subsystem-05.txt draft-ietf-secsh-publickey-subsystem-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 25, 2006. This Internet-Draft will expire on February 1, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
Secure Shell defines an authentication mechanism that is based on Secure Shell defines an authentication mechanism that is based on
public keys, but does not define any mechanism for key distribution. public keys, but does not define any mechanism for key distribution.
No common key management solution exists in current implementations. No common key management solution exists in current implementations.
This document describes a protocol that can be used to configure This document describes a protocol that can be used to configure
public keys in an implementation-independent fashion, allowing client public keys in an implementation-independent fashion, allowing client
software to take on the burden of this configuration. software to take on the burden of this configuration.
skipping to change at page 2, line 21 skipping to change at page 3, line 7
The public-key subsystem provides a server-independent mechanism for The public-key subsystem provides a server-independent mechanism for
clients to add public keys, remove public keys, and list the current clients to add public keys, remove public keys, and list the current
public keys known by the server. Rights to manage public keys are public keys known by the server. Rights to manage public keys are
specific and limited to the authenticated user. specific and limited to the authenticated user.
A public key may also be associated with various restrictions, A public key may also be associated with various restrictions,
including a mandatory command or subsystem. including a mandatory command or subsystem.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Public-Key Subsystem Overview . . . . . . . . . . . . . . . . 4 2. Public-Key Subsystem Overview . . . . . . . . . . . . . . . . 5
2.1. Opening the Public-Key Subsystem . . . . . . . . . . . . . 4 2.1. Opening the Public-Key Subsystem . . . . . . . . . . . . . 5
2.2. Requests and Responses . . . . . . . . . . . . . . . . . . 5 2.2. Requests and Responses . . . . . . . . . . . . . . . . . . 6
2.3. The Status Message . . . . . . . . . . . . . . . . . . . . 5 2.3. The Status Message . . . . . . . . . . . . . . . . . . . . 6
2.3.1. Status Codes . . . . . . . . . . . . . . . . . . . . . 5 2.3.1. Status Codes . . . . . . . . . . . . . . . . . . . . . 6
2.4. The Version Packet . . . . . . . . . . . . . . . . . . . . 6 2.4. The Version Packet . . . . . . . . . . . . . . . . . . . . 7
3. Public-Key Subsystem Operations . . . . . . . . . . . . . . . 7 3. Public-Key Subsystem Operations . . . . . . . . . . . . . . . 8
3.1. Adding a Public Key . . . . . . . . . . . . . . . . . . . 7 3.1. Adding a Public Key . . . . . . . . . . . . . . . . . . . 8
3.2. Removing a Public Key . . . . . . . . . . . . . . . . . . 10 3.2. Removing a Public Key . . . . . . . . . . . . . . . . . . 11
3.3. Listing Public Keys . . . . . . . . . . . . . . . . . . . 10 3.3. Listing Public Keys . . . . . . . . . . . . . . . . . . . 11
3.4. Listing Server Capabilities . . . . . . . . . . . . . . . 10 3.4. Listing Server Capabilities . . . . . . . . . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12 4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5.1. Registrations . . . . . . . . . . . . . . . . . . . . . . 13 5.1. Registrations . . . . . . . . . . . . . . . . . . . . . . 14
5.2. Names . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.2. Names . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.2.1. Conventions for Names . . . . . . . . . . . . . . . . 13 5.2.1. Conventions for Names . . . . . . . . . . . . . . . . 14
5.2.2. Future Assignments of Names . . . . . . . . . . . . . 13 5.2.2. Future Assignments of Names . . . . . . . . . . . . . 15
5.3. Request Names . . . . . . . . . . . . . . . . . . . . . . 14 5.3. Request Names . . . . . . . . . . . . . . . . . . . . . . 15
5.4. Response Names . . . . . . . . . . . . . . . . . . . . . . 14 5.4. Response Names . . . . . . . . . . . . . . . . . . . . . . 15
5.5. Attribute Names . . . . . . . . . . . . . . . . . . . . . 14 5.5. Attribute Names . . . . . . . . . . . . . . . . . . . . . 15
5.6. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 15 5.6. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 16
5.6.1. Conventions . . . . . . . . . . . . . . . . . . . . . 15 5.6.1. Conventions . . . . . . . . . . . . . . . . . . . . . 16
5.6.2. Initial Assignments . . . . . . . . . . . . . . . . . 15 5.6.2. Initial Assignments . . . . . . . . . . . . . . . . . 16
5.6.3. Future Assignments . . . . . . . . . . . . . . . . . . 15 5.6.3. Future Assignments . . . . . . . . . . . . . . . . . . 16
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1. Normative References . . . . . . . . . . . . . . . . . . . 16 6.1. Normative References . . . . . . . . . . . . . . . . . . . 17
6.2. Informative References . . . . . . . . . . . . . . . . . . 16 6.2. Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 18 Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Introduction 1. Introduction
Secure Shell is a protocol for secure remote login and other secure Secure Shell is a protocol for secure remote login and other secure
network services over an insecure network. Secure Shell defines an network services over an insecure network. Secure Shell defines an
authentication mechanism that is based on public keys, but does not authentication mechanism that is based on public keys, but does not
define any mechanism for key distribution. Common practice is to define any mechanism for key distribution. Common practice is to
authenticate once with password authentication and transfer the authenticate once with password authentication and transfer the
public key to the server. However, to date no two implementations public key to the server. However, to date no two implementations
use the same mechanism to configure a public key for use. use the same mechanism to configure a public key for use.
skipping to change at page 16, line 9 skipping to change at page 17, line 9
191 MUST be done through the Standards Action method as described in 191 MUST be done through the Standards Action method as described in
[9]. [9].
The IANA will not control the message numbers range of 192 through The IANA will not control the message numbers range of 192 through
255. This range will be left for private use. 255. This range will be left for private use.
6. References 6. References
6.1. Normative References 6.1. Normative References
[1] Ylonen, T. and C. Lonvick, "SSH Protocol Architecture", [1] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) Protocol
draft-ietf-secsh-architecture-22 (work in progress), March 2005. Architecture", RFC 4251, January 2006.
[2] Lonvick, C., "SSH Transport Layer Protocol", [2] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) Transport
draft-ietf-secsh-transport-24 (work in progress), March 2005. Layer Protocol", RFC 4253, January 2006.
[3] Lonvick, C. and T. Ylonen, "SSH Authentication Protocol", [3] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
draft-ietf-secsh-userauth-27 (work in progress), March 2005. Authentication Protocol", RFC 4252, January 2006.
[4] Lonvick, C. and T. Ylonen, "SSH Connection Protocol", [4] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) Connection
draft-ietf-secsh-connect-25 (work in progress), March 2005. Protocol", RFC 4254, January 2006.
[5] Alvestrand, H., "Tags for the Identification of Languages", [5] Alvestrand, H., "Tags for the Identification of Languages",
RFC 1766, March 1995. RFC 1766, March 1995.
[6] Yergeau, F., "UTF-8, a transformation format of ISO 10646", [6] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
RFC 2279, January 1998. RFC 2279, January 1998.
6.2. Informative References 6.2. Informative References
[7] Crocker, D., "Standard for the format of ARPA Internet text [7] Crocker, D., "Standard for the format of ARPA Internet text
skipping to change at page 18, line 5 skipping to change at page 19, line 5
Jon Bright Jon Bright
Silicon Circus Silicon Circus
24 Jubilee Road 24 Jubilee Road
Chichester, West Sussex PO19 7XB Chichester, West Sussex PO19 7XB
UK UK
Phone: +49 172 524 0521 Phone: +49 172 524 0521
Email: jon@siliconcircus.com Email: jon@siliconcircus.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 18, line 29 skipping to change at page 19, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 13 change blocks. 
61 lines changed or deleted 61 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/