Dynamic Remote Port forward?

Rogan Dawes rogan at dawes.za.net
Mon May 9 16:19:35 AEST 2016


Sorry, just wanted to add a Thank you. I appreciate you taking the time to
respond to my ramblings!

Rogan


On Mon, May 9, 2016 at 8:08 AM Rogan Dawes <rogan at dawes.za.net> wrote:

> That's what I thought! As mentioned, it would be awesome if this could be
> exposed as a Unix socket as well as a TCP port. I guess if you simply reuse
> the existing "port forward" code, that should come automatically?
>
> Rogan
>
>
> On Sun, May 8, 2016 at 10:34 PM Markus Friedl <mfriedl at gmail.com> wrote:
>
>>
>>
>> > Am 08.05.2016 um 21:27 schrieb Darren Tucker <dtucker at zip.com.au>:
>> >
>> >> On Sun, May 8, 2016 at 9:04 PM, Markus Friedl <mfriedl at gmail.com>
>> 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?
>> >
>>
>> Yes. That's better and the reason why my patch is ugly ;).
>> I'll look into doing this.
>>
>>
>> > --
>> > 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.
>>
>


More information about the openssh-unix-dev mailing list