Re: [tor-talk] New Tool Keeps Censors in the Dark - mentions Tor.
On 8/5/2011 4:42 PM, Martin Fick wrote: --- On Fri, 8/5/11, berta...@ptitcanardnoir.orgberta...@ptitcanardnoir.org wrote: http://www.technologyreview.com/communications/38207/?p1=A1 It's worth reading the paper: I think that simply getting high profile sites to run to r nodes would be more likely and less invasive to the internet as a whole. If google were to simply run a bunch of bridges, or even known tor entry nodes, that would likely be more reliable and be less pie in the sky. If you compare the advocacy it would take to get enough ISPs to implement this scheme versus the advocacy to get a few high profile (can't live without them) sites to run tor nodes, I suspect the latter would be much easier. -Martin You lost me at If google were to... Google privacy is the definition of an oxymoron. They're way down the list of organizations many users would want having any role in some anonymity endeavor. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
[tor-talk] Connection / socket issues with Tor on Mac OS
Hi all, so, I'd like to use Tor on my Mac, and access the web through its network of servers. So far so good, but as I'm familiar with Linux and the shell, I don't want to bring up Tor using the Vidalia GUI, but rather call it from Terminal and later on have both Tor and Polipo launched as daemons. So, I had a look at both the Torrc.sample file (Which I then renamed to torrc and moved to /Applications/Vidalia.app/tor). Also, I had a look at polipo.conf, however didn't change any of the settings. Then, I launched Tor as follows: Robins-MacBook-Air:MacOS owomac$ ./tor Aug 06 20:01:55.509 [notice] Tor v0.2.1.30. This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin x86_64) Aug 06 20:01:55.512 [notice] Initialized libevent version 2.0.10-stable using method kqueue. Good. Aug 06 20:01:55.512 [notice] Opening Socks listener on 127.0.0.1:9050 Aug 06 20:01:55.513 [notice] Parsing GEOIP file. Aug 06 20:01:55.938 [notice] OpenSSL OpenSSL 0.9.8p 16 Nov 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation Aug 06 20:01:57.392 [notice] We now have enough directory information to build circuits. Aug 06 20:01:57.392 [notice] Bootstrapped 80%: Connecting to the Tor network. Aug 06 20:01:58.635 [notice] Bootstrapped 85%: Finishing handshake with first hop. Aug 06 20:02:02.963 [notice] Bootstrapped 90%: Establishing a Tor circuit. Aug 06 20:02:03.924 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Aug 06 20:02:03.924 [notice] Bootstrapped 100%: Done. Afterwards, I launched Polipo in a separate process: Disabling disk cache: No such file or directory Disabling local tree: No such file or directory Established listening socket on port 8123. This, in itself, is already weird, as Polipo, by default, is supposed to bind to port 8118 as opposed to 8123. So then, when I configure the preferences for my network card and specify the web proxy and secure web proxy, I specify localhost as the hostname and 8123 as the port. When I confirm and apply the config changes, I can access the web just fine through Safari (I'm visually impaired, and unfortunately can't use Firefox on the Mac due to the lack of screen reader support). When I open a website such as Google in Safari after applying the new settings, the site loads just fine. However, when I open check.torproject.org, I get a message saying that I'm not using for. Also, browsing to a site like whatismyip.org shows my own IP, not the IP of a Tor server. When I change my proxy settings to port 8118, however, it doesn't work at all - Safari reports that it can't connect to the proxy. So then, I tried quitting both Tor and Polipo services and then launched the Vidalia GUI. This then reported that Tor was running, and in fact, when I set up proxy connectivity again and set the port to 8118, it worked just fine. I then tried removing the /Applications/Vidalia.app folder, the /Library/Vidalia folder and the ~/.tor folders. Afterwards, I tried setting up everything once again, however the issue is still present. So, when I call both the Tor and Polipo services from Terminal, Polipo obviously binds to a wrong port and seems to accept and forward connections, but they are not routed through Tor and thus Polipo isn't working properly. Only when both services are launched through the Vidalia GUI, everything seems to be just fine. So, what do I need to do in order to get them to work from Terminal? Thanks for any help! Robin ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Hijacking Advertising to give a Tor Exit node economic sustainability?
There's no way that would fly. People who are willing to buy advertising placements would not ever understand what Tor is and what audience size they could expect. Moreover, they would not want to participate in a scheme to substitute their ads for ads by others. They would have the feeling that the establishment would think of a way to bite them back for anything that interferes with its normal operation (advertising and brainwashing people). -- Jack ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Hijacking Advertising to give a Tor Exit node economic sustainability?
Fabio Pietrosanti (naif) wrote: Ok, modifying user traffic it's a tabu', but let's just consider for a moment how many useful things for the user and for the tor project could be done. Perhaps the user doesn't *want* those useful things done for him. Perhaps he knows what he is doing and is already doing *exactly* what he wants to do. Very slippery slope! (Not that I think there is a remote chance that such an exit node would not be marked as a bad exit just on general principles. I just wanted to point out that I find this nanny state attitude of we know better than you offensive. It's bad enough when ISPs break NXDOMAIN, etc. Although I doubt that you meant any harm. :-) Jim ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Connection / socket issues with Tor on Mac OS
Hi Jack, thanks for the idea! However, I'm really not sure if this really is the problem. After all, it actually works when Polipo is launched via the GUI, the problems only appear when I launch it from the command line. Also, Tor is set as the parent proxy in my Polipo config, but for some reason, it just doesn't work when I start them up from the shell. Any way I could maybe pinpoint the actual issue so that I can work on fixing it? Thanks! Robin ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Connection / socket issues with Tor on Mac OS
On Sat, 06 Aug 2011 20:17 +0200, Robin Kipp mli...@robin-kipp.net wrote: Hi all, so, I'd like to use Tor on my Mac, and access the web through its network of servers. So far so good, but as I'm familiar with Linux and the shell, I don't want to bring up Tor using the Vidalia GUI, but rather call it from Terminal and later on have both Tor and Polipo launched as daemons. So, I had a look at both the Torrc.sample file (Which I then renamed to torrc and moved to /Applications/Vidalia.app/tor). Also, I had a look at polipo.conf, however didn't change any of the settings. Then, I launched Tor as follows: Robins-MacBook-Air:MacOS owomac$ ./tor Aug 06 20:01:55.509 [notice] Tor v0.2.1.30. This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin x86_64) Aug 06 20:01:55.512 [notice] Initialized libevent version 2.0.10-stable using method kqueue. Good. Aug 06 20:01:55.512 [notice] Opening Socks listener on 127.0.0.1:9050 Aug 06 20:01:55.513 [notice] Parsing GEOIP file. Aug 06 20:01:55.938 [notice] OpenSSL OpenSSL 0.9.8p 16 Nov 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation Aug 06 20:01:57.392 [notice] We now have enough directory information to build circuits. Aug 06 20:01:57.392 [notice] Bootstrapped 80%: Connecting to the Tor network. Aug 06 20:01:58.635 [notice] Bootstrapped 85%: Finishing handshake with first hop. Aug 06 20:02:02.963 [notice] Bootstrapped 90%: Establishing a Tor circuit. Aug 06 20:02:03.924 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Aug 06 20:02:03.924 [notice] Bootstrapped 100%: Done. Afterwards, I launched Polipo in a separate process: Disabling disk cache: No such file or directory Disabling local tree: No such file or directory Established listening socket on port 8123. This, in itself, is already weird, as Polipo, by default, is supposed to bind to port 8118 as opposed to 8123. So then, when I configure the preferences for my network card and specify the web proxy and secure web proxy, I specify localhost as the hostname and 8123 as the port. When I confirm and apply the config changes, I can access the web just fine through Safari (I'm visually impaired, and unfortunately can't use Firefox on the Mac due to the lack of screen reader support). When I open a website such as Google in Safari after applying the new settings, the site loads just fine. However, when I open check.torproject.org, I get a message saying that I'm not using for. Also, browsing to a site like whatismyip.org shows my own IP, not the IP of a Tor server. When I change my proxy settings to port 8118, however, it doesn't work at all - Safari reports that it can't connect to the proxy. So then, I tried quitting both Tor and Polipo services and then launched the Vidalia GUI. This then reported that Tor was running, and in fact, when I set up proxy connectivity again and set the port to 8118, it worked just fine. I then tried removing the /Applications/Vidalia.app folder, the /Library/Vidalia folder and the ~/.tor folders. Afterwards, I tried setting up everything once again, however the issue is still present. So, when I call both the Tor and Polipo services from Terminal, Polipo obviously binds to a wrong port and seems to accept and forward connections, but they are not routed through Tor and thus Polipo isn't working properly. Only when both services are launched through the Vidalia GUI, everything seems to be just fine. So, what do I need to do in order to get them to work from Terminal? Thanks for any help! Robin ___ Are you pointing Polipo to the correct polipo.conf file when launching it from the command line? Such as /Applications/Vidalia.app/Contents/MacOS/polipo -c /Applications/Vidalia.app/Contents/Resources/polipo.conf ? GD -- http://www.fastmail.fm - Access your email from home and the web ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Hijacking Advertising to give a Tor Exit node economic sustainability?
For whatever it's worth, this seems to be a common model for a number of free VPN and Glype-style Web-based providers, who cater to clients attempting to get around content filtering. I've been interested in the mechanics and economics of the approach, but haven't yet had time to do any investigation. *CDA* On Sat, Aug 6, 2011 at 5:14 PM, Jim jimmy...@copper.net wrote: Fabio Pietrosanti (naif) wrote: Ok, modifying user traffic it's a tabu', but let's just consider for a moment how many useful things for the user and for the tor project could be done. Perhaps the user doesn't *want* those useful things done for him. Perhaps he knows what he is doing and is already doing *exactly* what he wants to do. Very slippery slope! (Not that I think there is a remote chance that such an exit node would not be marked as a bad exit just on general principles. I just wanted to point out that I find this nanny state attitude of we know better than you offensive. It's bad enough when ISPs break NXDOMAIN, etc. Although I doubt that you meant any harm. :-) Jim ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk -- *Collin David Anderson* averysmallbird.com | @cda | Washington, D.C. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Hijacking Advertising to give a Tor Exit node economic sustainability?
On Sun, Aug 7, 2011 at 12:06 AM, Dave Jevans wrote: AnchorFree is doing Multi-millions of dollars of business doing targeted ads on a free proxy/vpn service. I don't see why this couldn't be done with Tor. Didn't know about AnchorFree. I don't know how can the advertisers distinguish between impressions/clicks from different users if they have the same IP. They have to trust that they are not one AnchorFree employee refreshing the page with a script that changes the user agent. In our case, it would be difficult for Tor to build that trust because it will depend on each exit node. Quick question: can middle nodes modify traffic? If thats the case we have a bigger problem. ___ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
