Comments on: Tor needs bridge support testers http://anonymous.livelyblog.com/2007/08/01/tor-needs-bridge-support-testers/ Be Anonymous, Stay Anonymous, Live Anonymous Thu, 20 Nov 2008 17:51:54 +0000 http://wordpress.org/?v=2.6 By: Praedor Atrebates http://anonymous.livelyblog.com/2007/08/01/tor-needs-bridge-support-testers/#comment-83 Praedor Atrebates Wed, 26 Dec 2007 20:51:27 +0000 http://anonymous.livelyblog.com/2007/08/01/tor-needs-bridge-support-testers/#comment-83 Something above in a comment caught my eye: Aug 22 09:37:34.640 [Warning] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That’s bad! You should upgrade your Tor controller as soon as possible. How, exactly, does one "fix" this? I have perused the torrc file but nothing obvious pops out as to how to setup an authentication method so that things aren't "bad". How does one make this message/warning go away? Something above in a comment caught my eye:

Aug 22 09:37:34.640 [Warning] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That’s bad! You should upgrade your Tor controller as soon as possible.

How, exactly, does one “fix” this? I have perused the torrc file but nothing obvious pops out as to how to setup an authentication method so that things aren’t “bad”. How does one make this message/warning go away?

]]> By: panda http://anonymous.livelyblog.com/2007/08/01/tor-needs-bridge-support-testers/#comment-65 panda Fri, 31 Aug 2007 20:31:52 +0000 http://anonymous.livelyblog.com/2007/08/01/tor-needs-bridge-support-testers/#comment-65 XY, Your company proxy is almost certainly blocking HTTP connections to ports other than 80 and 443 (I have this problem too). I suggest that future bridges should be created on proxy-friendly ports. panda XY, Your company proxy is almost certainly blocking HTTP connections to ports other than 80 and 443 (I have this problem too).

I suggest that future bridges should be created on proxy-friendly ports.

panda

]]> By: Anonymous http://anonymous.livelyblog.com/2007/08/01/tor-needs-bridge-support-testers/#comment-64 Anonymous Wed, 22 Aug 2007 01:42:52 +0000 http://anonymous.livelyblog.com/2007/08/01/tor-needs-bridge-support-testers/#comment-64 Hi, I tried to test the bridge function. I'm behind a company firewall that blocks the dir-servers. I don't think the bridge function is working for me. This is in my torrc: SocksPort 9050 SocksListenAddress 127.0.0.1 #SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also #RunAsDaemon 1 #ControlPort 9051 HttpProxy xxxxxx:8080 HttpsProxy xxxxxxx:8080 #ReachableDirAddresses *:80 #ReachableORAddresses *:443 UseBridges 1 TunnelDirConns 1 Bridge 128.31.0.34:9009 4C17 FB53 2E20 B2A8 AC19 9441 ECD2 B017 7B39 E4B1 It doesn't matter if I use Http(s)Proxy, or not, the result is always the same. This is in the log: Aug 22 09:37:34.296 [Notice] Tor v0.2.0.4-alpha. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows 2000 Service Pack 4 [workstation]) Aug 22 09:37:34.640 [Warning] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible. Aug 22 09:37:34.640 [Notice] Initialized libevent version 1.3b using method win32. Good. Aug 22 09:37:34.640 [Notice] Opening Socks listener on 127.0.0.1:9050 Aug 22 09:37:34.750 [Notice] Opening Control listener on 127.0.0.1:9051 Aug 22 09:37:37.718 [Notice] no known bridge descriptors running yet; stalling Aug 22 09:39:35.718 [Notice] Freeing linked Socks connection [waiting for circuit] with 64 bytes on inbuf, 0 on outbuf. Aug 22 09:39:36.718 [Notice] no known bridge descriptors running yet; stalling Any suggestions that can help? Best regards, XY Hi,

I tried to test the bridge function. I’m behind a company firewall that blocks the dir-servers. I don’t think the bridge function is working for me.

This is in my torrc:
SocksPort 9050
SocksListenAddress 127.0.0.1
#SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also
#RunAsDaemon 1
#ControlPort 9051
HttpProxy xxxxxx:8080
HttpsProxy xxxxxxx:8080
#ReachableDirAddresses *:80
#ReachableORAddresses *:443
UseBridges 1
TunnelDirConns 1
Bridge 128.31.0.34:9009 4C17 FB53 2E20 B2A8 AC19 9441 ECD2 B017 7B39 E4B1

It doesn’t matter if I use Http(s)Proxy, or not, the result is always the same.

This is in the log:
Aug 22 09:37:34.296 [Notice] Tor v0.2.0.4-alpha. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows 2000 Service Pack 4 [workstation])
Aug 22 09:37:34.640 [Warning] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That’s bad! You should upgrade your Tor controller as soon as possible.
Aug 22 09:37:34.640 [Notice] Initialized libevent version 1.3b using method win32. Good.
Aug 22 09:37:34.640 [Notice] Opening Socks listener on 127.0.0.1:9050
Aug 22 09:37:34.750 [Notice] Opening Control listener on 127.0.0.1:9051
Aug 22 09:37:37.718 [Notice] no known bridge descriptors running yet; stalling
Aug 22 09:39:35.718 [Notice] Freeing linked Socks connection [waiting for circuit] with 64 bytes on inbuf, 0 on outbuf.
Aug 22 09:39:36.718 [Notice] no known bridge descriptors running yet; stalling

Any suggestions that can help?

Best regards, XY

]]>