That's pretty much what I was thinking. The most significant change will be that the client has to include the socks server code, which it doesn't currently (I suppose!). Or am I mistaken? Rogan On Sun, 8 May 2016, 21:27 Darren Tucker, <dtucker@xxxxxxxxxx> wrote: > On Sun, May 8, 2016 at 9:04 PM, Markus Friedl <mfriedl@xxxxxxxxx> wrote: > > I have an ugly patch for that feature that requires protocol > modification. > > Why does it require a protocol modification? Couldn't the client > request regular forwarded-tcpip from the server then decode SOCKS > entirely within the client? > > -- > Darren Tucker (dtucker at zip.com.au) > GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 > Good judgement comes with experience. Unfortunately, the experience > usually comes from bad judgement. > _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
