Sorry ... wasn't watching these pages much recently (except
CVS of course). I'm not sure what tool you want socks
support in.
If you mean statProxy, it's already there in test 18.
If you mean localproxy, then it's already there 'sort of'
(and has been there for years). You need to understand the
concept of 'abstraction' to appreciate this, i think. If you
tell LP to add a socks service, it will provide a localhost
port 11080 (by default) socks 4 proxy socket.You can use
this with socks 4 clients. This works the way many such
services work in LP - via CONNECT through the commStrat 1,
layer zero proxies. This covers 99% of users requirements
for socks. If no such proxies are available, the socks
service will be disabled.
The socks support I (meant to) talk about adding is possible
in different ways (adding socks code to LP and ensuring the
outside connection was unblocked, non-censoring, etc.,
adding code to start up ssh -D, etc.). I still haven't seen
a good reason for any of these other approaches.
Convince me. :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=184517
Sorry ... wasn't watching these pages much recently (except
CVS of course). I'm not sure what tool you want socks
support in.
If you mean statProxy, it's already there in test 18.
If you mean localproxy, then it's already there 'sort of'
(and has been there for years). You need to understand the
concept of 'abstraction' to appreciate this, i think. If you
tell LP to add a socks service, it will provide a localhost
port 11080 (by default) socks 4 proxy socket.You can use
this with socks 4 clients. This works the way many such
services work in LP - via CONNECT through the commStrat 1,
layer zero proxies. This covers 99% of users requirements
for socks. If no such proxies are available, the socks
service will be disabled.
The socks support I (meant to) talk about adding is possible
in different ways (adding socks code to LP and ensuring the
outside connection was unblocked, non-censoring, etc.,
adding code to start up ssh -D, etc.). I still haven't seen
a good reason for any of these other approaches.
Convince me. :-)