RE: SOCKS5 Support for CIPE-Win32?|
"Thomas Schulte" <Thomas.Schulte,AT,damovo,DOT,com>|
Fri, 28 Mar 2003 17:03:08 +0100|
Nope.. you do not :-)
Now: CIPE-Win32 >-----------------------------------------------> CIPE
CIPE-Win32 >----> Socks5 Server/Proxy >-------------------> CIPE
Just like the Linux version can do.
Have look at http://sites.inka.de/sites/bigred/sw/cipe-1.5.1.texinfo
or the cipe.info coming with
the functionality can be compared to an WEB-Proxy.
From: Damion K. Wilson [mailto:dwilson,AT,ibl,DOT,bm
Sent: Freitag, 28. März 2003 15:48
To: Thomas Schulte
Subject: Re: SOCKS5 Support for CIPE-Win32?
Oh, got it. You want CIPE to be able to request SOCKS to allow its packets
when it starts and turn them off on its way out. CIPE-Win32 supports startup
and shutdown scripts when an interface is enabled or disabled, if you have a
program that will do the SOCKS authentication, maybe you can run it from
On Friday 28 March 2003 02:50 am, you wrote:
> >Well, I doubt it. I'm not even sure what you mean by "SOCKS5 support"
> to be
> >honest. Can you elaborate on what you want to accomplish ?
> I just want to (have to) use a Socks5 Proxy with authentication to
> access the Internet from our company network.
> From cipe.info:
> Working with SOCKS
> With the `socks' option, CIPE uses a SOCKS5 server for sending and
> receiving the encrypted data. Since this is UDP, SOCKS4 (which doesn't
> support UDP) can not be used. SOCKS5 has a number of authentication
> methods. CIPE can use either no authentication or Username/Password.
> Username and password are taken from the environment variables
> `SOCKS5_USER' and `SOCKS5_PASSWD'.
> It would be nice if this feature would be implemented in CIPE-Win32 too!