Just a quick note on Tor and Build 116. This works so well.
There's a web page for help building/configuring the Tor client at: http://www.torproject.org/docs/tor-doc-unix.html.en Since 116 has a built in Tor client I skipped down to section 2, configuring privoxy. As instructed, I added forward-socks4a / 127.0.0.1:9050 . to the top of /etc/privoxy/config. Then: su - svcadm enable network/tor svcadm enable http:privoxy svcs -xv shows no errors Looking over /var/adm/messages shows the first message at 12:19 P.M. un 17 12:19:42 r51 Tor[13137]: [ID 702911 daemon.notice] Your Tor server's identity key fingerprint is 'r51 D9A6 3064 EDAC E9E9 F80F 1B53 6C7B D6B6 FC06 0093' Jun 17 12:19:43 r51 Tor[13137]: [ID 702911 daemon.notice] No current certificate known for authority moria1; launching request. At 12:31 I noticed this message show up: Jun 17 12:31:07 r51 Tor[13137]: [ID 702911 daemon.notice] I learned some more directory information, but not enough to build a circuit: We have only 378/1615 usable descriptors. Jun 17 12:31:17 r51 Tor[13137]: [ID 702911 daemon.notice] We now have enough directory information to build circuits. Since I had already installed the TorButton Firefox extension I clicked on the red "Tor Disabled" button. It changed to green and says "Tor Enabled." I surf to Google's home page and it's the Google homepage for Malaysia and not my normal English version. There is a bit of a performance hit and my auto logon button doesn't work anymore since the domain names no longer match up. I can click on "Tor Disabled", goto the site and use the auto logon button, and then enable Tor again to work around that. Nice job guys, alan -- This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list [email protected]
