resume.
tor rabotaet. posle zapuska iz komandnoi stroki rabotaet prekrasno socks5 server po adresu 127.0.0.1 i port 9050
odnako torify ne rabotaet iz za oshibok vyshe.
poetomu anonimnogo http browsinga ne vyjdet - v firefox tor rugnulsia chto on ne http proxy.
dlia polnocennoi reboty emu nuzhen eschio i privoxy. ili torify / tsocks.
v gaim i xchat nastroiki socks rabotyut:
* Looking up im.uk.bitlbee.org
* Looking up 127.0.0.1
* Connecting to 127.0.0.1 (127.0.0.1) port 9050...
* Connected. Now logging in...
GARBAGE: im.uk.bitlbee.org NOTICE AUTH :BitlBee-IRCd initialized, please go on
* Welcome to the BitlBee gateway,
openzaurus
tsocks, chto trebuetsia dlia raboty torify v debian linux tak i nazyvaetsia - tsocks i posle ruchnoi ustanovki paketa i bibliotek vsio poshlo.
esli vypuskat vsio eto velo v rc12 to nado kompilirovat
libevent
tor
tsocks
privoxy
socat
log raboty tor (sdelal torify links www.checkmyip.com):
Oct 17 18:42:35.610 [notice] Tor has successfully opened a circuit. Looks like it's working.
Oct 17 18:42:41.106 [warn] fetch_from_buf_socks(): Your application (using socks4 on port 80) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead.
Oct 17 18:42:50.931 [warn] fetch_from_buf_socks(): Your application (using socks4 on port 80) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead.
esli vypuskat vsio eto velo v rc12 to nado kompilirovat
libevent
tor
tsocks
privoxy
socat
log raboty tor (sdelal torify links www.checkmyip.com):
Oct 17 18:42:35.610 [notice] Tor has successfully opened a circuit. Looks like it's working.
Oct 17 18:42:41.106 [warn] fetch_from_buf_socks(): Your application (using socks4 on port 80) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead.
Oct 17 18:42:50.931 [warn] fetch_from_buf_socks(): Your application (using socks4 on port 80) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead.
