Re: [PATCH] SOCKS4A support - openssh

This is a discussion on Re: [PATCH] SOCKS4A support - openssh ; On Tue, 1 Jul 2008, David Woodhouse wrote: > This provides SOCKS4A support, which allows a SOCKS4 client to provide a > host name instead of an IP address. It indicates that it's doing so by > using a known-invalid ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: [PATCH] SOCKS4A support

  1. Re: [PATCH] SOCKS4A support

    On Tue, 1 Jul 2008, David Woodhouse wrote:

    > This provides SOCKS4A support, which allows a SOCKS4 client to provide a
    > host name instead of an IP address. It indicates that it's doing so by
    > using a known-invalid IP address 0.0.0.x (where x != 0), and then
    > appending the NUL-terminated hostname to the connection request.


    How many programs speak SOCKS4A and not SOCKS5?

    -d

    _______________________________________________
    openssh-unix-dev mailing list
    openssh-unix-dev@mindrot.org
    https://lists.mindrot.org/mailman/li...enssh-unix-dev


  2. Re: [PATCH] SOCKS4A support

    On Tue, 2008-07-01 at 20:39 +1000, Damien Miller wrote:
    > On Tue, 1 Jul 2008, David Woodhouse wrote:
    >
    > > This provides SOCKS4A support, which allows a SOCKS4 client to provide a
    > > host name instead of an IP address. It indicates that it's doing so by
    > > using a known-invalid IP address 0.0.0.x (where x != 0), and then
    > > appending the NUL-terminated hostname to the connection request.

    >
    > How many programs speak SOCKS4A and not SOCKS5?


    socat, for a start, which was the first thing I tried when I started
    trying to use SOCKS. Not sure what else.

    --
    dwmw2

    _______________________________________________
    openssh-unix-dev mailing list
    openssh-unix-dev@mindrot.org
    https://lists.mindrot.org/mailman/li...enssh-unix-dev


  3. Re: [PATCH] SOCKS4A support

    Damien Miller wrote:
    > On Tue, 1 Jul 2008, David Woodhouse wrote:
    >
    >
    >> This provides SOCKS4A support, which allows a SOCKS4 client to provide a
    >> host name instead of an IP address. It indicates that it's doing so by
    >> using a known-invalid IP address 0.0.0.x (where x != 0), and then
    >> appending the NUL-terminated hostname to the connection request.
    >>

    >
    > How many programs speak SOCKS4A and not SOCKS5?
    >

    There are a few -- and if I remember, they just always do SOCKS4A.
    Basically people assume that it's part of the SOCKS4 standard, given how
    absurdly trivial SOCKS4 itself is.

    --Dan

    _______________________________________________
    openssh-unix-dev mailing list
    openssh-unix-dev@mindrot.org
    https://lists.mindrot.org/mailman/li...enssh-unix-dev


+ Reply to Thread