Difference between revisions of "Summerschool Aachen 2004/Notes"
Mario Manno (talk | contribs) m (adding categories) |
Mario Manno (talk | contribs) |
||
| Line 54: | Line 54: | ||
After configuring dante, the "socksify" script can be used to make applications use the SOCKS proxy. | After configuring dante, the "socksify" script can be used to make applications use the SOCKS proxy. | ||
| − | [[ | + | [[Category:Summerschools]] |
Revision as of 14:24, 23 September 2004
General Notes about the Summerschool, Aachen, Software, whatever comes to your mind.
Lab Net
TSocks
If you still have trouble with socks i suggest the tsocks package, works nicely with openssh and apt-get. I guess you already know about proxy enviroment variables. dante is the other LD wrapper for socks.
Proxy ENV
export http_proxy=http://172.17.23.1:3128 export ftp_proxy=http://172.17.23.1:3128
Socat SSH
socat command line to get SSH working I used these commands to access SSH on $REMOTEMACHINE
$ socat TCP4-LISTEN:31228,reuseaddr \ SOCKS4:172.17.23.1:$REMOTEMACHINE:22,socksport=1080 $ ssh localhost -p31228
corkscrew
ilja@nikita:~/corkscrew-2.0%cat ~/.ssh/config ProxyCommand /home/ilja/corkscrew-2.0/corkscrew 172.17.23.1 3128 %h %p ilja@nikita:~/corkscrew-2.0%
dante
(Running on OpenBSD under VMWare, but should work anywhere...)
$ cat /etc/socks.conf
# have a route making all connections to loopback addresses be direct.
route {
from: 0.0.0.0/0 to: 127.0.0.0/8 via: direct
command: connect udpassociate # everything but bind, bind confuses us.
}
route {
from: 0.0.0.0/0 to: 172.17.23.0/24 via: direct
}
route {
from: 0.0.0.0/0 to: 0.0.0.0/0 via: 172.17.23.1 port = 1080
protocol: tcp udp # server supports tcp and udp.
proxyprotocol: socks_v4 socks_v5 # server supports socks v4 and v5.
method: none #username # we are willing to authenticate via
# method "none", not "username".
}
Note: On Debian/GNU Linux the config file is called /etc/dante.conf
After configuring dante, the "socksify" script can be used to make applications use the SOCKS proxy.
