- djm@cvs.openbsd.org 2008/06/30 12:18:34

[PROTOCOL]
     clarify that eow@openssh.com is only sent on session channels
This commit is contained in:
Darren Tucker 2008-07-02 22:33:16 +10:00
parent 8748b96522
commit 1f781b194f
2 changed files with 8 additions and 5 deletions

View File

@ -10,6 +10,9 @@
- djm@cvs.openbsd.org 2008/06/30 12:16:02
[nchan.c]
only send eow@openssh.com notifications for session channels; ok! markus@
- djm@cvs.openbsd.org 2008/06/30 12:18:34
[PROTOCOL]
clarify that eow@openssh.com is only sent on session channels
20080630
- (djm) OpenBSD CVS Sync
@ -4493,4 +4496,4 @@
OpenServer 6 and add osr5bigcrypt support so when someone migrates
passwords between UnixWare and OpenServer they will still work. OK dtucker@
$Id: ChangeLog,v 1.5041 2008/07/02 12:32:43 dtucker Exp $
$Id: ChangeLog,v 1.5042 2008/07/02 12:33:16 dtucker Exp $

View File

@ -46,9 +46,9 @@ processes of the condition, e.g. by closing the corresponding file
descriptor.
OpenSSH implements a channel extension message to perform this
signalling: "eow@openssh.com" (End Of Write). This message is sent by an
endpoint when the local output of a channel is closed or experiences a
write error. The message is formatted as follows:
signalling: "eow@openssh.com" (End Of Write). This message is sent by
an endpoint when the local output of a session channel is closed or
experiences a write error. The message is formatted as follows:
byte SSH_MSG_CHANNEL_REQUEST
uint32 recipient channel
@ -240,4 +240,4 @@ The values of the f_flag bitmask are as follows:
This extension is advertised in the SSH_FXP_VERSION hello with version
"2".
$OpenBSD: PROTOCOL,v 1.9 2008/06/28 14:08:30 djm Exp $
$OpenBSD: PROTOCOL,v 1.10 2008/06/30 12:18:34 djm Exp $