Package: tor
Version: 0.2.0.19-alpha-1
Severity: important
this update broke my access to freenode with irssi; I use this
configuration :
* $ alias
alias irssi='torify /usr/bin/irssi'
* $ cat /etc/tor/torrc
## Replace this with SocksPort 0 if you plan to run Tor only as a
## server, and not make any local application connections yourself.
SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
#SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also
## Send all messages of level 'notice' or higher to
/var/log/tor/notices.log
#perso
# http://freenode.net/irc_servers.shtml#tor
mapaddress 10.40.40.40 mejokbp2brhw4omd.onion
mapaddress 10.40.40.41 5t7o4shdbhotfuzp.onion
* irssi:
[(status)] /server +10.40.40.40
22:13 [10] -!- Irssi: Looking up 10.40.40.40
22:13 [10] -!- Irssi: Connecting to 10.40.40.40 [10.40.40.40] port 6667
22:15 [10] -!- Irssi: Connection lost to 10.40.40.40
[(status)] 22:15:33 libtsocks(6003): SOCKS V4 connect rejected:
* $ tail -f /var/log/tor/log
Feb 13 21:19:50.739 [warn] Your application (using socks4 to port 6667)
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.
For more information, please see
http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS.
Feb 13 21:20:34.064 [warn] Your application (using socks4 to port 6667)
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.
For more information, please see
http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS.
Feb 13 21:21:09.783 [notice] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'Zwerg2k'. Retrying on a new circuit.
Feb 13 21:21:24.863 [notice] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'nixnix'. Retrying on a new circuit.
Feb 13 21:21:39.916 [notice] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'nanelmoth'. Retrying on a new circuit.
Feb 13 21:21:54.976 [notice] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'jalopy'. Retrying on a new circuit.
Feb 13 21:22:16.056 [notice] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'BostonUCompSci'. Retrying on a new circuit.
Feb 13 21:22:32.112 [notice] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'jalopy'. Retrying on a new circuit.
Feb 13 21:22:34.120 [notice] Tried for 120 seconds to get a connection
to [scrubbed]:6667. Giving up.
Feb 13 22:15:33.040 [notice] Tried for 120 seconds to get a connection
to [scrubbed]:6667. Giving up. (waiting for rendezvous desc)
ask more if you need
thx for the help
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages tor depends on:
ii adduser3.105 add and remove users and groups
ii libc6 2.7-7 GNU C Library: Shared libraries
ii libevent1 1.3e-1An asynchronous event notification
ii libssl0.9.80.9.8g-4 SSL shared libraries
ii tsocks 1.8beta5-6transparent network access through
ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime
Versions of packages tor recommends:
ii privoxy 3.0.8-1Privacy enhancing HTTP Proxy
ii socat 1.6.0.0-1 multipurpose relay for bidirection
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
