IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
query about draft-ietf-secsh-connect-19.txt
In draft-ietf-secsh-connect-19.txt, Section 7.1, there is a reference
to:
byte SSH_MSG_GLOBAL_REQUEST_SUCCESS
uint32 port that was bound on the server
which should probably be "SSH_MSG_REQUEST_SUCCESS"
The other odd thing about this packet is that it's the only one which
doesn't encode the request type in which it's in response to.
This form would appear to make more sense:
byte SSH_MSG_REQUEST_SUCCESS
string "tcpip-forward"
uint32 port that was bound on the server
As this is the only packet for which the contents of the packet can
vary without a "constant field" on which to make the decision of which
further packets to inspect. In other cases, e.g. SSH_MSG_CHANNEL_REQUEST,
the decision to decode further fields can be taken by lookinng at the
first string argument.
--
Anil Madhavapeddy http://anil.recoil.org
University of Cambridge http://www.cl.cam.ac.uk
Home |
Main Index |
Thread Index |
Old Index