IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Other Socket Tunnels (Was: New draft Possibilities)
>> The extra name in there breaks the format of SSH_MSG_CHANNEL_OPEN.
>> Since you don't have any data specific to "direct-socket" apart from
>> that name, it would be better to just make it part of the channel
>> type (so "direct-udpip", "direct-unix", "direct-named-pipe").
> Alternatively, the following format works: [type name at end]
> (I'm not commenting on which would be better... just that both are
> legal.)
In case anyone cares what I think - I'd prefer one channel type with a
subtype field ("direct-socket" with "udp", "named-pipe", etc).
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse%rodents.montreal.qc.ca@localhost
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Home |
Main Index |
Thread Index |
Old Index