Tags: tor


  08:10:00 am, by The Dreamer   , 428 words  
Categories: General, Networking

Pinterest supports Internet Censorship

It has been about 20 months since I took the EFF Tor Challenge:

Operate a Tor relay to help Tor users all over the world!

Activists worldwide use Tor to protect their anonymity online and to circumvent Internet censorship. But they all rely on a limited number of user-provided "relays" to protect themselves and communicate with others. Internet users worldwide need your help to make the Tor network stronger and faster, so take the Tor Challenge today!

From this I initially set up two Tor relays....initially one with a limited set of exits and one with no exits (middle relay). For more info see: What is a Tor relay?

But, FreeNode blocks exit relay IPs that could access any of their systems....that includes port 80/http. Instead they run a hidden service that would allow a Tor user to connect to IRC via Tor....and say:

We appreciate your accessing Freenode via the Tor hidden service. If you'd like to help us maintain quality access, please consider providing "middleman" bandwidth to the Tor network. Just set your host up as a Tor server and specify how much bandwidth you want to provide.

I did irssi connecting to the hidden service as an experiment....while waiting for the exit relay block to expire. I continued to run irssi this way for a while, until I got tired of doing so.

Since then, Tor wise, I'm playing around with running an anonymous bridge in AWS.....currently costing under $1 each month on the free tier...for bandwidth overages. I'm wondering what it'll be after my free-tier expires, and what would happen if I were to move to another region. Though I guess its deploy new in another region and remove old, since the images have updated a number of times since my initial deployment that there have already been occasions where my image has had trouble staying current.

And, then recently I got stopped from accessing Pinterest, with "the we've detected a bot!", "because Bots may be resource-intensive and slow down Pinterest for other users."

After some email exchanges, they responded that:

Pinterest blocked access because the IP address originating traffic hosts a public Tor node. If you are knowingly hosting a public Tor node, we cannot ensure continued access if traffic coming through your node is malicious.

But, since its a middle relay, the only traffic originating from my IP address to Pinterest is me. So, they're censoring anybody that supports Tor and its use "as a method for whistleblowers and human rights workers to communicate with journalists"....

Guess, they're a strong supporter of Internet Censorship!


  09:52:32 pm, by The Dreamer   , 1090 words  
Categories: General, Software, Networking, Android

I took The EFF Tor Challenge

Link: http://www.eff.org/torchallenge

Earlier in the week, I got an email from EFF about their Tor Challenge. I had looked at Tor some time ago, but it seemed like a hassle to use. But, I am a support of EFF, and not just because I had lots of ReplayTVs and now a few TiVos.

So, I decided to take another look at Tor....I had started worrying about my privacy with some of my online activities, and I do support various human rights issues, etc.

The challenge called for setting up a relay. So, I continued looking and what I needed to do to make it do that. ORPort prefers to be either 9001 or 443...well, wouldn't go on 9001 on Orac, it conflicted with another service that I'm already running. So, it would have to go on a different port.

That, meant figuring out how to NAT on my WRT54GS...it doesn't do port NAT on inbound forwards, so I had to figure out how to add entries to iptables to make that go. That took some doing, but eventually I got that working. Not before I accidentally lost my rc_firewall, and had to restore for a rather old version. I should probably see about doing some kind of automated backup...

It defaults to going with exit relay, and I decided to go ahead...but use the 'reduced exit relay' policy. To see how that would work.

I set bandwidth and transfer limits on things....but first instance on the 'Orac' actually hit the limit, which made it hard to night surf for my own reasons. And, while I was on the torproject site, I decided to take a look at Orbot for both my Android phone and my Android tablet. And, I suppose I'll want to run it on my laptop.

One problem I seemed to have is that I couldn't get tor to work locally on my android phone on wifi, but it worked on 3g. I figured its some kind of conflict with the tor network seeing the relay at the same IP. Though later it started working, maybe that was the relay went into hibernation. I did set up 'Orac' as a central proxy for everything at home. Strange that when I think of private surfing I tend to use my DSL and general surfing on Cox. I had gone with default gateway on 'Orac'...so it was going Cox.

With everything seeming to work well, I opted to set up another instance of 'box' to use my other Internet connection. That didn't go as well, because the ISP blocks a lot more inbound connections than the other. But, I got it working. And, I poked around some sites here and there before calling it a night.

Pages: 1· 2

Now instead of subjecting some poor random forum to a long rambling thought, I will try to consolidate those things into this blog where they can be more easily ignored profess to be collected thoughts from my mind.

Latest Poopli Updaters -- http://lkc.me/poop


There are 20 years 7 months 24 days 34 minutes and 10 seconds until the end of time.
And, it has been 4 years 5 months 4 days 13 hours 28 minutes and 46 seconds since The Doctor saved us all from the end of the World!


May 2017
Mon Tue Wed Thu Fri Sat Sun
 << <   > >>
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31        


  XML Feeds

Who's Online?

  • Guest Users: 2
This seal is issued to lawrencechen.net by StopTheHacker Inc.

hosted by
Green Web Hosting! This site hosted by DreamHost.

monitored by
Monitored by eXternalTest
SiteUptime Web Site Monitoring Service
website uptime