draft-ietf-secsh-connect-06.txt   draft-ietf-secsh-connect-07.txt 
Network Working Group T. Ylonen Network Working Group T. Ylonen
INTERNET-DRAFT T. Kivinen INTERNET-DRAFT T. Kivinen
draft-ietf-secsh-connect-06.txt M. Saarinen draft-ietf-secsh-connect-07.txt M. Saarinen
Expires in six months T. Rinne Expires in six months T. Rinne
S. Lehtinen S. Lehtinen
SSH SSH Communications Security
22 June 1999 11 May 2000
SSH Connection Protocol SSH Connection Protocol
Status of This Memo Status of This memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. with all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at page 10, line 52 skipping to change at page 10, line 52
boolean want reply boolean want reply
string subsystem name string subsystem name
This last form executes a predefined subsystem. It expected that these This last form executes a predefined subsystem. It expected that these
will include a general file transfer mechanism, and possibly other will include a general file transfer mechanism, and possibly other
features. Implementations may also allow configuring more such features. Implementations may also allow configuring more such
mechanisms. mechanisms.
The server SHOULD not halt the execution of the protocol stack when The server SHOULD not halt the execution of the protocol stack when
starting a shell or a program. All input and output from these SHOULD be starting a shell or a program. All input and output from these SHOULD be
redirected the the channel or to the encrypted tunnel. redirected to the channel or to the encrypted tunnel.
It is RECOMMENDED to request and check the reply for these messages. The It is RECOMMENDED to request and check the reply for these messages. The
client SHOULD ignore these messages. client SHOULD ignore these messages.
4.8. Session Data Transfer 4.8. Session Data Transfer
Data transfer for a session is done using SSH_MSG_CHANNEL_DATA and Data transfer for a session is done using SSH_MSG_CHANNEL_DATA and
SSH_MSG_CHANNEL_EXTENDED_DATA packets and the window mechanism. The SSH_MSG_CHANNEL_EXTENDED_DATA packets and the window mechanism. The
extended data type SSH_EXTENDED_DATA_STDERR has been defined for stderr extended data type SSH_EXTENDED_DATA_STDERR has been defined for stderr
data. data.
skipping to change at page 12, line 40 skipping to change at page 12, line 40
uint32 recipient channel uint32 recipient channel
string "exit-signal" string "exit-signal"
boolean FALSE boolean FALSE
uint32 signal number uint32 signal number
boolean core dumped boolean core dumped
string error message (ISO-10646 UTF-8 [RFC-2044]) string error message (ISO-10646 UTF-8 [RFC-2044])
string language tag (as defined in [RFC-1766]) string language tag (as defined in [RFC-1766])
The `error message' contains an additional explanation of the error The `error message' contains an additional explanation of the error
message. The message may consist of multiple lines. The client software message. The message may consist of multiple lines. The client software
MAY display this message to the user. MAY display this message to the user. If this is done, the client
software should take the precautions discussed in [SSH-ARCH].
5. TCP/IP Port Forwarding 5. TCP/IP Port Forwarding
5.1. Requesting Port Forwarding 5.1. Requesting Port Forwarding
A party need not explicitly request forwardings from its own end to the A party need not explicitly request forwardings from its own end to the
other direction. However, it if wishes to have connections to a port on other direction. However, if it wishes to have connections to a port on
the other side be forwarded to the local side, it must explicitly the other side be forwarded to the local side, it must explicitly
request this. request this.
byte SSH_MSG_GLOBAL_REQUEST byte SSH_MSG_GLOBAL_REQUEST
string "tcpip-forward" string "tcpip-forward"
boolean want reply boolean want reply
string address to bind (e.g. "0.0.0.0") string address to bind (e.g. "0.0.0.0")
uint32 port number to bind uint32 port number to bind
`Address to bind' and `port number to bind' specify the IP address and `Address to bind' and `port number to bind' specify the IP address and
skipping to change at page 17, line 8 skipping to change at page 17, line 8
Since this protocol normally runs inside an encrypted tunnel, firewalls Since this protocol normally runs inside an encrypted tunnel, firewalls
will not be able to examine the traffic. will not be able to examine the traffic.
It is RECOMMENDED that implementations disable all of the potentially It is RECOMMENDED that implementations disable all of the potentially
dangerous features (e.g. agent forwarding, X11 forwarding, and TCP/IP dangerous features (e.g. agent forwarding, X11 forwarding, and TCP/IP
forwarding) if the host key has changed. forwarding) if the host key has changed.
9. Trademark Issues 9. Trademark Issues
SSH is a registered trademark and Secure Shell is a trademark of SSH SSH is a registered trademark and Secure Shell is a trademark of SSH
Communications Security Ltd. SSH Communications Security Ltd permits Communications Security Corp. SSH Communications Security Corp permits
the use of these trademarks as the name of this standard and protocol, the use of these trademarks as the name of this standard and protocol,
and permits their use to describe that a product conforms to this and permits their use to describe that a product conforms to this
standard, provided that the following acknowledgement is included standard, provided that the following acknowledgement is included where
where the trademarks are used: ``SSH is a registered trademark and the trademarks are used: ``SSH is a registered trademark and Secure
Secure Shell is a trademark of SSH Communications Security Ltd Shell is a trademark of SSH Communications Security Corp
(www.ssh.fi)''. These trademarks may not be used as part of a product (www.ssh.com)''. These trademarks may not be used as part of a product
name or in otherwise confusing manner without prior written permission name or in otherwise confusing manner without prior written permission
of SSH Communications Security Ltd. of SSH Communications Security Corp.
10. References 10. References
[RFC-1766] Alvestrand, H., "Tags for the Identification of Languages", [RFC-1766] Alvestrand, H., "Tags for the Identification of Languages",
March 1995. March 1995.
[RFC-1884] Hinden, R., and Deering, S., "IP Version 6 Addressing [RFC-1884] Hinden, R., and Deering, S., "IP Version 6 Addressing
Architecture", December 1995 Architecture", December 1995
[RFC-2044] Yergeau, F., "UTF-8, a Transformation Format of Unicode and [RFC-2044] Yergeau, F., "UTF-8, a Transformation Format of Unicode and
ISO 10646", October 1996. ISO 10646", October 1996.
[SSH-ARCH] Ylonen, T., et al, "SSH Protocol Architecture", Internet [SSH-ARCH] Ylonen, T., et al, "SSH Protocol Architecture", Internet
Draft, draft-ietf-secsh-architecture-04.txt Draft, draft-ietf-secsh-architecture-05.txt
[SSH-TRANS] Ylonen, T., et al, "SSH Transport Layer Protocol", Internet [SSH-TRANS] Ylonen, T., et al, "SSH Transport Layer Protocol", Internet
Draft, draft-ietf-secsh-transport-06.txt Draft, draft-ietf-secsh-transport-07.txt
[SSH-USERAUTH] Ylonen, T., et al, "SSH Authentication Protocol", [SSH-USERAUTH] Ylonen, T., et al, "SSH Authentication Protocol",
Internet Draft, draft-ietf-secsh-userauth-06.txt Internet Draft, draft-ietf-secsh-userauth-07.txt
11. Authors' Addresses 11. Authors' Addresses
Tatu Ylonen Tatu Ylonen
SSH Communications Security Ltd. SSH Communications Security Corp
Tekniikantie 12 Fredrikinkatu 42
FIN-02150 ESPOO FIN-00100 HELSINKI
Finland Finland
E-mail: ylo@ssh.fi E-mail: ylo@ssh.com
Tero Kivinen Tero Kivinen
SSH Communications Security Ltd. SSH Communications Security Corp
Tekniikantie 12 Fredrikinkatu 42
FIN-02150 ESPOO FIN-00100 HELSINKI
Finland Finland
E-mail: kivinen@ssh.fi E-mail: kivinen@ssh.com
Markku-Juhani O. Saarinen Markku-Juhani O. Saarinen
SSH Communications Security Ltd. University of Jyvaskyla
Tekniikantie 12
FIN-02150 ESPOO
Finland
E-mail: mjos@ssh.fi
Timo J. Rinne Timo J. Rinne
SSH Communications Security Ltd. SSH Communications Security Corp
Tekniikantie 12 Fredrikinkatu 42
FIN-02150 ESPOO FIN-00100 HELSINKI
Finland Finland
E-mail: tri@ssh.fi E-mail: tri@ssh.com
Sami Lehtinen Sami Lehtinen
SSH Communications Security Ltd. SSH Communications Security Corp
Tekniikantie 12 Fredrikinkatu 42
FIN-02150 ESPOO FIN-00100 HELSINKI
Finland Finland
E-mail: sjl@ssh.fi E-mail: sjl@ssh.com
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/