IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Other misc things in the drafts
"Joseph Galbraith" <galb-list%vandyke.com@localhost> writes:
> - In the connection draft, section 4.3.1, we should note
> that the x11 authentication cookie MUST be hexadecimal
> encoded.
Why? Is that what people are doing (I haven't implemented x11
forwarding yet). It seems very strange to me to use a redundant but
ascii-friendly encoding for things in the binary very eight-bit clean
ssh protocols.
> - In the connection draft, section 5.1, we should specify
> text like this:
>
> The response to the "tcpip-forward" request will look like:
>
> byte SSH_MSG_GLOBAL_REQUEST_SUCCESS
> string "tcpip-forward"
> uint32 port that was bound on server
>
> We should also explicitly allow binding to port
> 0 to indicate any port.
I agree this is a good idea. Although I think that for backwards
compatibility we should either
(i) say that the port field is included *only* when binding port 0,
or
(ii) use a new request type
/Niels
Home |
Main Index |
Thread Index |
Old Index