openssh unix dev - Jun 2003 - Patch for Socks5 support for dynamic portforwaring?

oldsleepi wrote:
> Hi,
> 
> has anybody seen a patch that provides socks version 5 support for the
dynamic portforwarding feature?
> I?ve seen thats implemented in ssh.com?s ssh version, but
> found nothing about openssh.
> Only thing i found was a patch to provide socks4a.
check the mailing list archives.

-d

> has anybody seen a patch that provides socks version 5 support for the
dynamic portforwarding feature?
why?  we removed that feature:

http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/channels.c.diff?r1=1.108&r2=1.109

Hi,

has anybody seen a patch that provides socks version 5 support for the dynamic
portforwarding feature?
I?ve seen thats implemented in ssh.com?s ssh version, but
found nothing about openssh.
Only thing i found was a patch to provide socks4a.

cu

sleepi

Hi,
just to enlighten my ignorance ;-)

Why was Socks5 support removed from openssh?

I also could see some useful applications for SOCKS5 over SSH ...

- alex

-----Ursprungliche Nachricht-----
Von: openssh-unix-dev-bounces+openssh=peuchert.de at mindrot.org
[mailto:openssh-unix-dev-bounces+openssh=peuchert.de at mindrot.org]Im
Auftrag von Markus Friedl
Gesendet: Dienstag, 24. Juni 2003 12:51
An: oldsleepi
Cc: openssh-unix-dev at mindrot.org
Betreff: Re: Patch for Socks5 support for dynamic portforwaring?

> has anybody seen a patch that provides socks version 5 support for the
dynamic portforwarding feature?

why?  we removed that feature:

http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/channels.c.diff?r1=1.1
08&r2=1.109

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev at mindrot.org
http://www.mindrot.org/mailman/listinfo/openssh-unix-dev

>
> On Thu, Jun 26, 2003 at 09:29:16PM +0200, Alex Peuchert wrote:
> > Concerning UDP via SOCKS5: according to the RFC1928, UDP datagrams are
> > encapsulated in an UDP request and then sent over a Stream
> (which is exactly
> > what ssh provides). This does not sound like having to invent
> something new.
>
> but who decapsulates
SOCKS5 is the protocol between the SOCKS client and the SOCKS5 server;
always TCP => stream
the rest is up to the server

On Thu, Jun 26, 2003 at 09:44:54PM +0200, Alex Peuchert
wrote:
> 
> 
> >
> > On Thu, Jun 26, 2003 at 09:29:16PM +0200, Alex Peuchert wrote:
> > > Concerning UDP via SOCKS5: according to the RFC1928, UDP
datagrams are
> > > encapsulated in an UDP request and then sent over a Stream
> > (which is exactly
> > > what ssh provides). This does not sound like having to invent
> > something new.
> >
> > but who decapsulates
> 
> SOCKS5 is the protocol between the SOCKS client and the SOCKS5 server;
> always TCP => stream
> the rest is up to the server
but sshd will not talk UDP.

> > 
> > SOCKS5 is the protocol between the SOCKS client and the SOCKS5 server;
> > always TCP => stream
> > the rest is up to the server
> 
> but sshd will not talk UDP.
> 
why not?

On Thu, 26 Jun 2003, Alex Peuchert wrote:
> > >
> > > SOCKS5 is the protocol between the SOCKS client and the SOCKS5
server;
> > > always TCP => stream
> > > the rest is up to the server
> >
> > but sshd will not talk UDP.
> >
>
> why not?
>
Because no where in the RFC does it discuss how to handle UDP, just TCP.

- Ben

On Thu, 26 Jun 2003, Alex Peuchert wrote:
> > >
> > > SOCKS5 is the protocol between the SOCKS client and the SOCKS5
server;
> > > always TCP => stream
> > > the rest is up to the server
> >
> > but sshd will not talk UDP.
>
> why not?
get a clue.

You are asking for features without the slightest understanding of
their implementation, implications or appropriateness.

-d