- tor-relays - lists.torproject.org

A call to arms for obfuscated bridges
by George Kadianakis 06 May '13

06 May '13

Greetings, A year ago we asked you to run obfuscated bridges to help people in Iran [0]. Many people answered our call and we ended up having a big pool of obfuscated bridges to give to our users. Unfortunately, today, most of those bridges are down, and fresh ones are needed more than ever, since obfuscated bridges are the only way for people to access Tor in some areas of the world (like China, Iran and Syria). On the bright side, Tor's anti-censorship infrastructure has improved, and now you don't have to send the bridge addresses to us; if you run an obfuscated bridge with Tor 0.2.4.x, Tor will send its own address to BridgeDB [1] like normal bridges do. Also, obfsproxy was rewritten in Python and it now supports a new pluggable transport called 'obfs3' which works even in China [2]. We have dropped support for the C-version of Obfsproxy, and the new Pluggable Transport Bundles contain the Python version [3]. Finally, future pluggable transports will be developed for the Python version. Looking into BridgeDB, we have 200 obfs2 bridges, but only 40 obfs3 bridges: this means that we need more people running the new Python obfsproxy! Upgrading obfsproxy should be easy now, since we prepared new instructions and Debian/Ubuntu packages. If you run Debian or Ubuntu check out these instructiosn: https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en otherwise use these: https://www.torproject.org/projects/obfsproxy-instructions.html.en (and make sure your pip is upgraded so that it uses HTTPS [4]) Furthermore, Tor's support assistants need some _unpublished_ bridges to give to censored users who ask for help via email. To configure an unpublished bridge you add "PublishServerDescriptor 0" to its torrc. After you do so, fire up Tor, and check its logs to find the ports that 'obfs2' and 'obfs3' are using. Send your IP and ports to tor-assistants(a)torproject.org. Finally, if in the future we need you to do something extra (for example to upgrade obfsproxy to support a new pluggable transport) we will send another mail to tor-relays. Thanks for the help! [0]: https://lists.torproject.org/pipermail/tor-talk/2012-February/023070.html [1]: https://bridges.torproject.org [2]: In China obfs2 is blocked using active probes: https://trac.torproject.org/projects/tor/ticket/8591 [3]: https://blog.torproject.org/blog/new-name-obfsproxy-tor-browser-bundles [4]: https://groups.google.com/forum/#!msg/python-virtualenv/foXxh-NpdGg/uT0NPc9…

14 26

Support for Relay Operators (signed)
by Moritz Bartl 04 May '13

04 May '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The last mail was not signed, because the Mail Merge addon does not work together with Enigmail. Sorry. - ---- cut ---- Hi, I just noticed that I never announced that we offer support for relay operators at support [at] torservers [dot] net. You can encrypt your mails using PGP -- https://www.torservers.net/torservers_pub.asc fingerprint B099 CF5D 5B97 DC65 2406 B458 C8F4 2EB2 E033 4E90 Currently, four founding members of Torservers.net read that address. If you are a "Torservers partner", please think about joining the support team. We can use your help! - -- Moritz Bartl https://www.torservers.net/ -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJRg7atAAoJEOGPxWJITcUAHc4H/2mv6Wlpg5bLA5aHTx7lFn19 Dfgr2NTslfwRSA5CO3HeGRytoEoZUJ1xiZMh3SNZzLB6241WxBhdp5mExXFgTe0e E4WFP9rcDVSY2wuzi9QkjergQy3oeaadL17eiRs//GK+eb9wcBfpZ8OHyCTrauln dTUWVCAdtglptTed4Kx2ZUEPjHVoA9pWr9DQ9mxJjXLbREiu4ru0acC7QYswBj/r zt44LfkqPwEOzCrnvqEKOLT/MPP1lPk27tq7dfsTTozdII7VsrVj+nxdoWsfbFOp MyWe7240q4+0QOxHddWXMAAOgnnHOT+QfMeK1BYc1/FBosm9TAVVQmSQvbsb0HU= =BuJ9 -----END PGP SIGNATURE-----

3 3

Support for Relay Operators
by Moritz Bartl 03 May '13

03 May '13

Hi, I just noticed that I never announced that we offer support for relay operators at support [at] torservers [dot] net. You can encrypt your mails using PGP -- https://www.torservers.net/torservers_pub.asc fingerprint B099 CF5D 5B97 DC65 2406 B458 C8F4 2EB2 E033 4E90 Currently, four founding members of Torservers.net read that address. If you are a "Torservers partner", please think about joining the support team. We can use your help! -- Moritz Bartl https://www.torservers.net/

1 0

Preparation for reimbursement: partner mailinglists
by Moritz Bartl 03 May '13

03 May '13

Hi, In preparation of Torservers.net reimbursing exit and bridge operators, we have set up two new mailing lists. Entities that receive reimbursement are called "Torservers partners" and listed at https://www.torservers.net/partners.html (if they want to be listed) If you want to become a partner, we have to get to know you first: Ideally, we have personally met you multiple times, and learned about your motives. I announce these lists publicly, because the list archives of both lists are *public* and you are welcome to use them. You can send messages to the discussion list, but they will be moderated. The list called "partners" is *compulsory* if you want to receive reimbursements, as it will be used for important announcements that *must* be read by all participating entities. The list "partners-discuss" is optional. Subscription is limited to partners, so you are free to use it for whatever you want to discuss with other partners. If you are a member of a participating organization, you can subscribe and we will confirm your membership (moderated subscription). Summary of list options: partners: - important announce list! - *public* archive - subscription for anyone, but *required* for partners - moderated posting, so you can reach all members with important notices, but only after verification - subscription list private - reply-to set to partners-discuss https://www.torservers.net/services/mailman/listinfo/partners partners-discuss: - *public* archive - subscription and posting for partners only - subscription list private https://www.torservers.net/services/mailman/listinfo/partners-discuss Emails by non-members are *rejected*. If you want to reach partner organizations, please use the public mailinglist at http://www.freelists.org/list/torservers . It will be read at least by Torservers "staff". -- Moritz Bartl https://www.torservers.net/

1 0

Any operators in Singapore?
by Sanjeev Gupta 25 Apr '13

25 Apr '13

Hi, I run a number of Tor Relays, including exit nodes, in Singapore. I have recieved a request from the Singapore Police, who are investigating a case of "unauthorised payments via Paypal". They have asked for the customer to whom I have assigned the IP address (the request is because I am the whois contact for the network). Is there any other Singapore operator on the list who has experience? -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane

2 2

Using the name of a named node
by Konstantinos Asimakis 25 Apr '13

25 Apr '13

https://atlas.torproject.org/#details/A84D7DF9D58E0FAFF8CCC06A6A49DD96BD1DF… https://atlas.torproject.org/#details/12404BB1BB4F09CA65B76D77F347BC0D79CB7… How is this possible? I though that if you try to take the name of an unnamed node, your node switched to Unnamed or something like that automatically. Does the named flag prohibit other nodes from taking that name, or is it merely enabling clients to refer to you by name unambiguously? ----- My blog: http://www.inshame.com My full signature with lots of links etc: http://bit.ly/trtsig

2 1

Restart relay daily
by peckman＠hushmail.com 23 Apr '13

23 Apr '13

Hi! I am running a middle-man relay on a Raspberry Pi averaging 700 kBps. The board is very limited in processing power and memory. After some days, maybe a week, the Tor daemon runs out of memory and I have to start it manually again. I have tried different Tor versions, built alphas with and without the --enable-openbsd-malloc but it's no measurable difference; eventually a bad malloc will terminate the program. To solve this I have added a cron job to restart the daemon on a daily basis. Is this an OK solution? Traffic-wise it takes around 30 minutes to get back to normal throughput but the alternative is long downtimes until I notice the crash. Will there be any problem with the directory interaction? Relay info: Fast Guard Named Running Stable V2Dir Valid Tor 0.2.4.11-alpha Kind Regards, peckman

2 1

Re: [tor-relays] [tor-talk] NPA to urge Internet providers to block users of hijacking software [Tor]
by grarpamp 22 Apr '13

22 Apr '13

>> http://mainichi.jp/english/english/newsselect/news/20130418p2a00m0na013000c… "to voluntarily block communications if an anonymous software system ... is found abused online." The second ripline leaves some room but is without specifics. > It seems they are blurring the line between recommending that websites > refuse to answer connections from the Tor network, vs recommending that > ISPs prevent their users from reaching the Tor network. "The panel specifically recommends that communications be blocked when there is access from IP addresses publicly listed as those allocated to the third in a chain of computers that are used by Tor." This quote clears that up to be the former. However, it appears they also intend to ask network operators to block exits as well, not just websites: http://mainichi.jp/select/news/20130418k0000e040232000c.html "Based on the recommendations, the National Police Agency to encourage voluntary efforts such as the industry of Internet connection operators." They don't seem to say whether non-exits (thus the EG's among them) would remain accessible or not. "The Tor system was utilized by citizens in pro-democracy movements in the Middle East to escape government suppression, while Wikileaks also recommends Tor to information providers. The planned access restrictions are therefore expected to spark a backlash from the industry. 'Communication privacy is our lifeline. We won't be able to accept such a request,' said an industry insider. An NPA official said, 'We will make detailed explanations and seek their understanding.'" http://mainichi.jp/select/news/20130124k0000e040166000c.html "police were summarized for the strengthening of cyber crime investigation the 'emergency program' ... According to the National Police Agency, the police has been promoting public-private partnerships with such Internet-related companies so far, but pointed out that investigation and not keep up with the rapid advances in information and communication technology ... In the future, expanding the range to exchange personal level regardless of the occupation of the other party, and that improve the information collection... Emergency program, mentioned considerations and be entrusted to the private sector, the analysis of the modus operandi of education and other investigators" It's a little unclear to what degree these groups are for enforcement or education, whether they attend public conferences, etc. Likely the usual mix. There could be some good opportunities there. Cracking, corp/finance, data theft, copyright that sort of deal is one thing. But these idiots making death/bomb threats and such are really getting old not just on its face but due to their tendency to make the news and piss people off, and against Tor, in a different sort of way. I presume exit operators in Japan could ask NPA/Mainichi for the full panel doc and would be very interested in following this issue ... cc'd.

1 0

What is "regular" traffic on an obfuscated bridge
by Torry Torah 19 Apr '13

19 Apr '13

Hi there, After seeing the call to arm [1], I decided to spin up some 2 new obfuscated bridges. I am already running 2 (non-obf) bridges, and was about to boot 3 others. I'm seeing something like 4MB/day of traffic with those obf bridges, whereas the 2 non-obf bridges show something like 10MB/sec. ( All the servers more or less have the same specs, so it's not a hardware/connectivity issue. My question is: is it a "normal" amount of traffic on an obf bridge? For what it's worth, I followed intructions here [2] on an ubuntu precise with a firewall. I allowed communications on the OR port and the 2 ports given by obf2 and obf3. I've set up the 2 obf bridges 8 hours ago, give or take, maybe is it just a matter of insufficient uptime? Cheers, [1] https://lists.torproject.org/pipermail/tor-relays/2013-April/002089.html [2] https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en

4 5

Trying to set up an obfs2/3 bridge on Windows, missing something.
by Asa Rossoff 18 Apr '13

18 Apr '13

I think I'm suppling the ServerTransport parameters incorrectly. the log seems to indicate it is listening on the wrong ports for obfs2 and obfs3. Since it was the only compiled package I saw for Windows with obfs support, I downloaded the tor-pluggable-transports-browser-2.4.11-alpha-2. I am using the following .torrc -- Address *obfuscated* AvoidDiskWrites 1 BridgeRelay 1 LearnCircuitBuildTimeout 0 CircuitBuildTimeout 60 ClientTransportPlugin websocket exec flashproxy-client --register :0 :56833 *[not useful, I realize]* ContactInfo *obfuscated* ControlPort 9051 CookieAuthentication 1 DataDirectory *obfuscated* DirPort 0 DirReqStatistics 0 ExitPolicy reject *:* GeoIPFile *obfuscated*/geoip GeoIPv6File *obfuscated*/geoip6 HardwareAccel 1 ServerTransportPlugin obfs2,obfs3 exec pyobfsproxy managed ServerTransportListenAddr obfs2,obfs3 0.0.0.0:56831 0.0.0.0:56832 Log notice stdout Nickname *obfuscated* NumCPUs 4 ORPort 56830 RelayBandwidthBurst 97280 RelayBandwidthRate 71680 SocksListenAddress 127.0.0.1 SocksPort 9050 I get the following log messages on starting Tor: [Notice] Tor v0.2.4.11-alpha (git-fcd9248387249d68) running on Windows 7 with Libevent 2.0.21-stable and OpenSSL 1.0.0k. [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning [Notice] This version is not a stable Tor release. Expect more bugs than usual. [Notice] Read configuration file "*obfuscated*\torrc". [Notice] Opening Socks listener on 127.0.0.1:9050 [Notice] Opening Control listener on 127.0.0.1:9051 [Notice] Opening OR listener on 0.0.0.0:56830 [Notice] Parsing GEOIP IPv4 file *obfuscated*/geoip. [Notice] Parsing GEOIP IPv6 file *obfuscated*/geoip6. [Notice] Your Tor server's identity key fingerprint is '*obfuscated* *obfuscated*' [Notice] We now have enough directory information to build circuits. [Notice] Bootstrapped 80%: Connecting to the Tor network. [Notice] New control connection opened. [Notice] Bootstrapped 85%: Finishing handshake with first hop. [Notice] Registered server transport 'obfs3' at '0.0.0.0:60093' [Notice] Registered server transport 'obfs2' at '0.0.0.0:60094' [Notice] Bootstrapped 90%: Establishing a Tor circuit. [Notice] Tor has successfully opened a circuit. Looks like client functionality is working. [Notice] Bootstrapped 100%: Done. I have ports 56830, 56831, 56832, and 56833 forwarded to this machine from my router/nat. I get connections on my ORPort 56830 -- though in 2-3 days, not a single client. Seems to be directory exchanges (?) or my own Tor Browser use. Isn't 2-3 days long enough to be discovered? Looks like it is listening on 60093 and 60094 for obfs3 and obfs2 instead of the intended 56832 and 56831 (the ports I have forwarded) for the purpose. Any help? Is it just a syntax error on my part (I tried using two lines for the ServerTransportListenAddr but one was automatically deleted after editing in Vidalia), or am I further off-track? Thanks a bundle :) Asa

2 2

Tor node monitoring
by Alex Beal 17 Apr '13

17 Apr '13

Hello All, I was wondering what, if any, software you use for monitoring your relays. It would be nice if I could get an email when the Tor daemon crashes, and maybe another every night telling me about bandwidth used, average speed, etc. Thanks, Alex -- For sensitive information, use my public key: http://media.usrsb.in/files/pub.asc Fingerprint: 0BCE 27F8 FBED 34C0 B936 7625 1D7D CA76 C811 1C0C

6 5

Tor Relay on DSL connection
by Jochen 16 Apr '13

16 Apr '13

Hello, I'm running a tor relay (non-exit) on DSL connection. My ISP reconnects me every 24 hours and gives me a new ip. How must tor be configured to publish it's new ip address after reconnect? Can tor daemon (linux) do this automatically or do I have to run a cron job and restart service cron at specific times?

3 2

I need to shut down my relay for a month possibly, what should I do
by Nate Homier 15 Apr '13

15 Apr '13

I'm upgrading my internet to a static IP setup with custom reverse DNS, which is perfect for my relay as then all complaints go to the contact info in the reverse DNS, which would be me. However I'm leaving on a month long trip and if the upgrade won't happen before April 17th 9 AM, I probably will half to shut down the server for a month. The server would be turned back on about May 25th or 30th. If I shut down for a month what will happen to my relay. What if someone chooses the same nick for their relay and so on. Nate

3 3

BitTorrent complaint
by bartels 13 Apr '13

13 Apr '13

Hi People, Two days ago I opened two fast tor exit relays v2.3 on debian wheezy. Now I get complaints from paramount that I have unwittingly distributed Hansel and Gretel via BitTorrent <Port>39585</Port> <Type>BitTorrent</Type> Can this be linked to tor, or is that impossible? I don't want to shut down tor for no reason. - Bartels.

11 40

On the way to more diversity
by Moritz Bartl 12 Apr '13

12 Apr '13

Hi, I have started to make changes to the Torservers.net website to reflect that we have grown from "professional Tor Exit hosting" to a state where growth of a single organization is not useful any more. We have refrained from ramping up more exit capacity for quite some time because of that. With the help of TorProject Inc., and by being an example for others to follow, we can now refer to multiple organizations, and become an "umbrella organization" that distributes funds across these organizations. Legally, we might be able to offer "abuse handling services" for exit operators. I will discuss this with our lawyer, and keep you updated. With the German charitable Wau Holland Foundation, we have found a first great partner for the "new" Torservers.net. Instead of donating directly to us, you can now donate to the project account at Wau Holland Foundation. Hopefully, we can find even more partners in the future. All partner organizations have been chosen carefully. We will iron out details on how we distribute funds so we get a more diverse Tor network. Please, talk to us if you want to set up a similar organization. https://www.torservers.net/partners.html https://www.torservers.net/donate.html The next step is to also professionalize bridges hosting. It is quite a shame that we only have a few hundred bridges in total. The situation got worse now that regular bridges are blocked in several countries, and in China only obfs3 bridges work -- of which we only have a few. We are actively on the lookout for sponsors interested in funding bridges. -- Moritz Bartl https://www.torservers.net/

7 9

big spike in cpu usage
by Owen Gunden 12 Apr '13

12 Apr '13

I have been running a non-exit tor relay for a few months now. It's on a metered VPS, so after some experimenting I found that I can afford about this much bandwidth: RelayBandwidthRate 250 KB RelayBandwidthBurst 500 KB This worked fine until recently. However, just today I noticed the machine was sluggish, and sure enough tor was using 99% cpu and dumping these messages to syslog: Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [2022 similar message(s) suppressed in last 60 seconds] Digging deeper, I've seen these messages pop up from time to time over the last 30 days or so, but not consistently, and I've never noticed the cpu pegged (but it could have happened, I don't use the machine that often). I tried including: MaxAdvertisedBandwidth 50 KB and # https://lists.torproject.org/pipermail/tor-relays/2012-May/001352.html MaxOnionsPending 250 to no avail. I have had to dial all the way down to: RelayBandwidthRate 40 KB RelayBandwidthBurst 80 KB and that seems to make the messages go away, but the cpu is still pegged and the machine is sluggish. It's running on an up-to-date debian squeeze (6.0.7), with tor 0.2.3.25-1~~squeeze+1 and openssl 0.9.8o-4squeeze14. I run updates fairly often. I upgraded to this version of tor a couple of weeks ago, which could be related, but doesn't correlate perfectly to when I first find the "too slow" messages in my logs. The only other recent updates that seem plausibly related are libbind/libisc/libisccc/etc.

9 15

Relay overload
by cmeclax 11 Apr '13

11 Apr '13

I noticed when sshing to my relay box that it is responding much slower than normal - taking a minute or two to respond to a single keypress. I ran netstat -t and saw lots of bytes in the outqueue to various other relays. I telnetted to port 9051 and got the following bandwidth log: 650 BW 63449 10568 650 BW 62510 21671 650 BW 63433 22438 650 BW 40314 19035 650 BW 94448 61126 650 BW 10408 11154 650 BW 123157 58027 650 BW 62837 31070 650 BW 12002 3536 650 BW 159449 65423 650 BW 64487 23865 650 BW 65471 35381 650 BW 68892 21466 650 BW 65378 46215 650 BW 38807 11434 650 BW 90042 43329 650 BW 65909 44768 650 BW 77162 18627 650 BW 107393 56922 650 BW 67305 36924 650 BW 25255 11149 650 BW 79619 37266 650 BW 123230 25956 650 BW 67194 27742 650 BW 70871 49787 650 BW 62114 50882 650 BW 53981 60433 650 BW 42699 21631 650 BW 161246 77324 650 BW 66421 39994 650 BW 68306 51876 650 BW 37977 21411 650 BW 157806 71560 650 BW 67964 35298 650 BW 64643 38299 650 BW 41193 26601 650 BW 156710 106887 650 BW 18786 14135 650 BW 158192 48526 650 BW 62862 39633 650 BW 67273 38448 650 BW 57955 39696 650 BW 34695 28979 650 BW 156069 81872 650 BW 53572 28598 650 BW 159163 43722 650 BW 65412 41567 650 BW 67271 48134 650 BW 65372 46107 650 BW 36323 14414 650 BW 0 0 650 BW 158006 92438 650 BW 64455 56813 650 BW 53169 11364 650 BW 109892 82106 650 BW 65191 34845 650 BW 12916 10803 650 BW 76387 21984 650 BW 0 0 650 BW 91819 54140 650 BW 63323 43265 650 BW 66760 26847 650 BW 12030 5817 650 BW 62995 16102 650 BW 154965 70999 650 BW 68408 38650 650 BW 87724 30290 650 BW 44543 45024 650 BW 60544 35343 650 BW 103227 35954 650 BW 155268 53094 650 BW 64928 37615 650 BW 66599 33239 650 BW 111463 36394 650 BW 76657 67405 650 BW 65448 40502 650 BW 65778 49605 650 BW 23300 7620 650 BW 155335 70596 650 BW 65994 31356 650 BW 66109 27590 650 BW 158464 72332 650 BW 60705 36345 650 BW 102858 25936 650 BW 161401 24083 650 BW 86788 62280 650 BW 66162 54081 My throughput limit is 64K, which has not previously been a problem. I've sometimes seen steady throughput close to 64K; more often it's sporadic with an average around 5K. Any idea what's going on? I checked Blutmagie; I've lost the fast flag, but have not been selected as guard or any other new flag. I thought it might have something to do with the bitcoin crash that's going on, but netstat -t on the bitcoin box doesn't show any similar attempt to push more data than the line can handle. If I were selected as the middleman in one user's file upload, I'd see a steady stream of traffic, not this spikiness. cmeclax

1 0

Re: [tor-relays] How to limit number of sockets used?
by Roman Mamedov 10 Apr '13

10 Apr '13

On Wed, 10 Apr 2013 07:51:57 -0400 Steve Snyder <swsnyder(a)snydernet.net> wrote: > Yes, I have hit the limit, with the expected "Error creating network > socket: No buffer space available" messages seen. Afaik this is a different error, and it comes from the RAM limit for network buffers, not due to hitting the maximum quantity of open sockets. ConstrainedSockets/ConstrainedSockSize may actually help you here. Also next time you hit this error, check "lsof -n | grep tor | wc -l". My guess is it will be much lower than 4096. -- With respect, Roman

1 0

How to limit number of sockets used?
by Steve Snyder 10 Apr '13

10 Apr '13

I am running Tor v0.2.3.25 in a VPS that limits me to a max of 4096 sockets in use. How can I instruct Tor not to attempt to use more than this number? Yes, I know about ConstrainedSockets/ConstrainedSockSize, but the way I read these it limits the amount of memory used, not the socket count. Advice, please? Thanks.

5 5

Can you double check my exit policy for usefulness while minimizing complaints
by Nate Homier 09 Apr '13

09 Apr '13

I was wondering if I have a good compromise between not allowing BitTorrent and allowing enough ports to be useful. Here's mine. ExitPolicy accept *:119 # accept nntp as well as default exit policy ExitPolicy accept *:22 # ssh ExitPolicy accept *:80 # www ExitPolicy accept *:443 # www secure ExitPolicy accept *:110 # pop3 ExitPolicy accept *:143 # imap ExitPolicy accept *:995 # pop3 secure ExitPolicy accept *:6660-6669 # irc ExitPolicy accept *:6697 # irc ssl ExitPolicy accept *:7000-7001 # irc ssl ExitPolicy accept *:706 # silc ExitPolicy accept *:1863 # msn ExitPolicy accept *:5050 # yahoo messenger ExitPolicy accept *:5190 # various im programs ExitPolicy accept *:5222 # various im programs ExitPolicy accept *:5223 # various im programs ExitPolicy accept *:8300 # im ExitPolicy accept *:8888 # www ExitPolicy accept *:465 # smtps (SMTP over SSL) ExitPolicy accept *:993 # imaps (IMAP over SSL) ExitPolicy accept *:994 # ircs (IRC over SSL) ExitPolicy reject *:* # no exits allowed How does this compare with this policy located here: https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy Should I use the official Tor reduced policy or is mine good enough to be useful while minimizing complaints. Nate

2 2

tor cpu usage
by Martin Weinelt 09 Apr '13

09 Apr '13

Hey, I'm running a tor relay with version 0.2.4.11-alpha and there seems to be an issue about cpu usage. Usually when the bandwidth peaks (at about 10 MBit/s) the cpu is at about 25-35% load, however after a few days it gets stuck at 100%. The notices-logfile, to my knowledge, does not indicate any weirdness. I'm attaching the "[warn]" section though: Apr 04 18:19:16.000 [warn] crypto error while checking RSA signature: block type is not 01 (in rsa routines:RSA_padding_check_PKCS1_type_1) Apr 04 18:19:16.000 [warn] crypto error while checking RSA signature: padding check failed (in rsa routines:RSA_EAY_PUBLIC_DECRYPT) Apr 06 20:38:18.000 [warn] Tried to establish rendezvous on non-OR or non-edge circuit. Apr 06 21:01:05.000 [warn] Tried to establish rendezvous on non-OR or non-edge circuit. Apr 07 04:35:49.000 [warn] eventdns: Unable to add nameserver 2001:4860:4860::8888: error 2 Apr 07 04:35:49.000 [warn] eventdns: Unable to add nameserver 2001:4860:4860::8844: error 2 Unfortunately I don't do any statistics so I can't relate a specific event with the spiking cpu load. Does anybody else experience this? What could cause this? How can I fix it? Martin

1 0

How Can I Do This?
by Barack Obama 08 Apr '13

08 Apr '13

My website, Bypass-Censorship.org, is getting LOTS of spam traffic from Tor (specifically in the wp-cron.php script). I obviously don't want to block Tor as it's extremely beneficial for privacy geeks and people from Iran, China, etc, to access my site; however, I do have an alternative solution that I may need help with. Basically what I want to do is add some PHP code in the beginning of index.php (I use WordPress as my CMS). What the code should do is detect if the client is using Tor, and if the client is, the script redirects to the mobile version of my site (mobile.dudamobile.com/site/bypass-censorship - it is hosted for free on DudaMobile). I believe this would be beneficial for two reasons: 1. Spam attacks and hack attacks are useless since it is not on my primary host (meaning there is no wp-cron.php). 2. And it will take a huge load off my server (I am well-ranked for the term "hidden wiki" in Google and Ixquick). Please tell me what you think of this idea, and how I can implement it. Thanks, -BC

4 3

Advice on configuring Obfsproxy3 transport?
by Steve Snyder 06 Apr '13

06 Apr '13

Attempting to get Obfsproxy3 to work. With Tor v0.2.4.11-alpha and Obfsproxy pulled from https://git.torproject.org/obfsproxy.git yesterday this is what I get at runtime: Apr 05 14:57:23.000 [warn] Server managed proxy encountered a method error. (obfs3 could not setup protocol) Apr 05 14:57:23.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed the configuration protocol and will be destroyed I have no problems with obfs2, but obfs3 success continues to elude me. These are the relevant lines from my bridge config: ServerTransportListenAddr obfs3 aaa.bb.cc.dd:12647 ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy --managed Any advice on how to get Obfsproxy to work would be greatly appreciated. Thanks.

2 1

Obfsproxy doesn't use specified addresses?
by Steve Snyder 05 Apr '13

05 Apr '13

I've got a server with 2 IP addresses, and a bridge running on each address. I followed the instructions for using Obfsproxy, adding this line to each Tor config file: ServerTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed It seems that Obfsproxy is not running on a per-address basis but instead each instance is bound to all addresses. (See below). Is this really how it is supposed to work? Shouldn't each instance of Obfsproxy be bound to a specific IP address? ----------------- # lsof -ni | grep _tor tor TCP aaa.aa.aa.aa:https (LISTEN) tor TCP aaa.aa.aa.aa:57242->000.00.000.000:https (ESTABLISHED) tor TCP aaa.aa.aa.aa:48851->111.111.111.11:torrouting (ESTABLISHED) tor TCP aaa.aa.aa.aa:34865->222.22.222.222:torrouting (ESTABLISHED) tor TCP bbb.bb.bb.bb:https (LISTEN) tor TCP bbb.bb.bb.bb:42826->333.33.333.33:https (ESTABLISHED) tor TCP bbb.bb.bb.bb:https->444.4.444.444:58519 (ESTABLISHED) tor TCP bbb.bb.bb.bb:33745->55.55.555.55:https (ESTABLISHED) tor TCP bbb.bb.bb.bb:44772->666.666.666.666:https (ESTABLISHED) obfsproxy TCP *:34866 (LISTEN) obfsproxy TCP *:41887 (LISTEN)

1 0

Re: [tor-relays] Too-regular traffic
by eliaz＠riseup.net 01 Apr '13

01 Apr '13

Never mind - I noticed the bookkeeping during a period when my bridge was carrying very low traffic. On 03.29.2013 eliaz wrote: > My bridge relay often shows regular pulses in its bandwidth graph, as > per the attached. Do these represent some housekeeping on the > network? [attachment scrubbed]

1 0