search for: vvviperrr

Hi, Currently, OpenSSH only accepts the SOCKS5 command "CONNECT": <https://anongit.mindrot.org/openssh.git/tree/channels.c#n1281> The RFC also specifies the commands "BIND" and "UDP ASSOCIATE": <https://tools.ietf.org/html/rfc1928#section-4> As a consequence, in particular, a SOCKS5 server started with "ssh -D" cannot proxify UDP packets. Are

...ately, if UDP packets are not relayed, it does not work. An alternative would be to use a tun device on the host and forward the packets (what SimpleRT? does), but this requires root access on the host. Regards, ?om ? <https://tools.ietf.org/html/rfc1928#section-7> ? <https://github.com/vvviperrr/SimpleRT>

...roblem for this use case is that it requires root-equivalent > access on both client and server to set up and open the tunnel devices. Yes, it would require root access on the server. It would be quite equivalent to what SimpleRT does, by creating a tun device manually. <https://github.com/vvviperrr/SimpleRT> Regards, ?om

On Jan 17, 2017, at 1:37 AM, Darren Tucker <dtucker at zip.com.au> wrote: > On Tue, Jan 17, 2017 at 8:05 PM, Romain Vimont <rom at rom1v.com> wrote: > [..] >> So if I understand correctly, making "ssh -D" create a "full" SOCKS5 >> server, including UDP relay?, would require to add a new SSH request >> type (like "relay-udp")? >