- tor-relays - lists.torproject.org

Operating a sponsored relay
by Dude 29 Aug '12

29 Aug '12

Hello, I have experience working at ISPs supporting dedicated servers and am interested in operating a sponsored relay. Potential issues I see: # A true 100mb network connection is going to be expensive. Often a 24 port edge switch has just one 100mb uplink port. # As an operator, I might want an LLC to protect me from personal liability in the USA. # Ideally an ISP outside the USA would be used so the server is in a different legal jurisdiction than the operator. This would make payment and communication more difficult. At this time I imagine a server with an encrypted file system and long term log retention disabled. Reasonably hardened OS, but nothing too exotic. I think $100 a month above other costs would be fair. But I do not know how much attention a node would require once it was set up. If it requires a lot of time, more compensation would be in order. I am not looking to make a lot of money doing this, but I can not do it gratis. Cheers, John

2 1

Re: [tor-relays] "Relay info kit" for Tor exits at universities
by Scott Bennett 25 Aug '12

25 Aug '12

On Sat, 11 Aug 2012 04:08:57 -0400 Roger Dingledine <arma(a)mit.edu> wrote: >I've spent the week talking to my contacts at US universities, to get >them to spin up fast exits. Currently the fast exits in North American >universities are: > >- University of Waterloo (Ian Goldberg) >- Boston University (Leo Reyzin) > >We're now on track to add: >- UPenn (Matt Blaze) >- UMichigan (Alex Halderman) >- CMU (Nicolas Christin) >- Georgia Tech (Dave Dagon) > >and I have professors from George Mason, Illinois, UNM, UMN, UConn, >UW, and others looking into it. > >Wendy and I are talking to some lawyers to try to write up a short >(several paragraph) document targeted toward the university's general >counsel, for preemptive use by the computer science professors who plan >to run the Tor exit. > >What else should go in a "so you want to run a big exit" info kit? > >- Pointers to the legal-faq (and dmca template) and abuse-faq. > >- Pointers to Mike's blog entry: >https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment >and my old Tor-at-universities wiki page: >https://trac.torproject.org/projects/tor/wiki/doc/TorGuideUniversities > >- Is there some document suggesting how to SWIP your address, and >explaining the importance of having your abuse mails go to someplace >other than your general university abuse team? It's touched on in several >places but we should make it even clearer. > >- What are the good answers now to "what hardware should I use, and how >should I configure it?" I've been telling people they'll be happiest with >Debian, and that something 64-bit and/or with AESNI support will be best. Fast relays use lots of memory, which vastly worsens the effects of the "small TLB" problem inherent in all modern CPUs, so running a fast relay on a FreeBSD kernel with superpages support enabled is likely to reduce considerably the CPU load for the traffic served, which is more or less equivalent to increasing the traffic capacity for any given CPU speed. Superpages support has been available since 7.2 for i386 and amd64 platforms, but will likely be available on other platforms at some point. Support on another platform was supposed to appear in 9.0, IIRC, but I don't remember which (ia64?). I'm not sure what will be in later releases, but my understanding is that the kernel development team planned to add superpages support eventually to the rest of the FreeBSD-supported hardware platforms that are capable of it (not, for example, powerpc because that hardware does not support the multiple page sizes involved). Rather than risk triggering OS religious wars here, it might be better to limit OS recommendations to merely which to avoid because they have limitations likely to prevent successful operation of a fast exit node (e.g., non-server versions of Windows). The administrators of fast nodes already know what their current setups are and the current knowledge bases of their staffs are. > >- [remainder deleted -SB] Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************

1 0

"Relay info kit" for Tor exits at universities
by Roger Dingledine 24 Aug '12

24 Aug '12

I've spent the week talking to my contacts at US universities, to get them to spin up fast exits. Currently the fast exits in North American universities are: - University of Waterloo (Ian Goldberg) - Boston University (Leo Reyzin) We're now on track to add: - UPenn (Matt Blaze) - UMichigan (Alex Halderman) - CMU (Nicolas Christin) - Georgia Tech (Dave Dagon) and I have professors from George Mason, Illinois, UNM, UMN, UConn, UW, and others looking into it. Wendy and I are talking to some lawyers to try to write up a short (several paragraph) document targeted toward the university's general counsel, for preemptive use by the computer science professors who plan to run the Tor exit. What else should go in a "so you want to run a big exit" info kit? - Pointers to the legal-faq (and dmca template) and abuse-faq. - Pointers to Mike's blog entry: https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment and my old Tor-at-universities wiki page: https://trac.torproject.org/projects/tor/wiki/doc/TorGuideUniversities - Is there some document suggesting how to SWIP your address, and explaining the importance of having your abuse mails go to someplace other than your general university abuse team? It's touched on in several places but we should make it even clearer. - What are the good answers now to "what hardware should I use, and how should I configure it?" I've been telling people they'll be happiest with Debian, and that something 64-bit and/or with AESNI support will be best. - We should set up a mailing list for university relay operators to share experiences and feel solidarity. I'll also encourage them to sign up here. We might also post a list of university Tor exits somewhere obvious, so new ones can gain more confidence in the idea. What other resources exist already that would be especially useful for new fast exits? What resources don't exist but should? --Roger

7 14

exit node with different IP address
by cmeclax-sazri 22 Aug '12

22 Aug '12

I rebooted my computer with a freshly compiled kernel and world, brought up my browser, and before doing something where I need to know my IP address is hidden, brought up check.torproject.org. It said "You are not using Tor." But the address is 217.148.84.179, which isn't anywhere near me. So I brought up torstatus.blutmagie.de and searched the page. It lists AMORPHIS at 217.148.84.180. I don't see ExitAddress in torrc. Should there be one? cmeclax

2 1

hi
by P.H. H 19 Aug '12

19 Aug '12

tor-relays(a)lists.torproject.org

2 1

Notice of disruption of service
by Dennis Ljungmark 17 Aug '12

17 Aug '12

Hi all, I'm sad to say that I've been forced to disable three of our six relays, and reduce the others to minimal transfer speeds. We are currently being exhorted by our ISP, Bahnhof for a huge amount of money due to "excessive traffic" in order to sign us up on a new contract. This should serve as a warning call for people who are using or considering to use Bahnhof. Contact take(a)deklomp.se for more information about the case. The affected nodes are: ( Reduced speed ) depth 9EDB9965625A06F41D84581BF66CAF7D79919DC4 vandalise 8D3E65A90F455E77DEFAA9ACEAFD7392221E2C9C deklomp1 0A9CB1B43C780634B80390A9093C7490CB503880 ( Offline until the issues are resolved ) deklomp2 EFA394DD66A8147AAEF3604B37CBF77DE2C7D895 deklomp3 FB5BECE11DDCE8444CB2EB0A41303DBB7093EA7A deklomp4 2403121E35A830A7131C388EB643915F06842FB4 Regards, D.S. "Spider" Ljungmark

2 2

Help the Tor Project by running a fast unpublished bridge
by Roger Dingledine 16 Aug '12

16 Aug '12

Hi folks, In addition to the "get many fast exit relays" plan, that same funder (Voice of America) wants us to run a pile of fast stable unpublished bridges. We'll give the bridge addresses out manually to their target users over the coming months. The constraints are: * 100mbit+ connectivity, though in practice I expect they will spend most of their time doing far less than that. * No more than 2 bridges per /24. If you're running fast (100mbit+) exits (which is more important), exits on that /24 count toward this 2. * No more than 7 bridges total per data center. If you could set up 1 (or 2, or 20) and send me the address(es) privately, that would be grand. We do have some funding for this, but I'm hoping that we can get enough volunteers so we can put the money toward more fast exits and better QA and build automation for the Tor bundles. So if you have good connectivity but can't run an exit, this is a great way to contribute. The torrc lines we want include: ORPort 443 # or whichever port you like BridgeRelay 1 PublishServerDescriptor 0 RelayBandwidthRate 11875 KB # or more RelayBandwidthBurst 12500 KB # or more If you have 3+ IP addresses and want to get fancy, you might set OutboundBindAddress to a different IP address than you tell me, to avoid some of the bridge enumeration attacks listed at https://blog.torproject.org/blog/research-problems-ten-ways-discover-tor-br… Later I might ask you to set up some sort of server-side pluggable transport like obfsproxy, but there's no rush on that. Long-term, "get a bunch of fast bridges on individual static IP addresses" is not a very good plan. Instead, we plan to focus on borrowing whole netblocks from ISPs and other people who aren't using them, and redirecting the addresses en masse into a bridge. You can start playing around with this idea by using an iptables rule rather than a bridge: /sbin/iptables -t nat -A PREROUTING -p tcp -d 18.244.0.114 --dport 80 -j DNAT --to-destination 128.31.0.34:9032 if the bridge listens on 128.31.0.34:9032 and you want me to advertise the address 18.244.0.114:80. Let me know if you have any questions or I can help clarify anything. Thanks! --Roger

9 19

Exit Port Usage Statistics for "Allow all" nodes
by Moritz Bartl 15 Aug '12

15 Aug '12

Hi, At torservers.net, we run some large exit relays with an "allow all except port 25" policy. These are statistics from ARM showing exit port statistics of a fast exit running for seven hours at 30-40 MB/s: 443 HTTPS 17650 (%55) 80 HTTP 10625 (%33) 8344 739 (%2) 8333 84 51413 45 6881 Torrent 38 8337 29 993 IMAPS 23 45682 18 182 16 9001 16 4662 eMule 14 4661 12 -- Moritz Bartl https://www.torservers.net/

4 4

Using aes-in in Tor
by tor-admin 15 Aug '12

15 Aug '12

Hi, I am struggling setting up aes-in support with Ubuntu 12.04 LTS. I enabled aes in bios. cat /proc/cpuinfo shows the aes flag. #lsmod |grep aes aesni_intel 55664 0 cryptd 20530 1 aesni_intel aes_x86_64 17208 1 aesni_intel shows that the module is loaded. But #openssl engine (rsax) RSAX engine support (dynamic) Dynamic engine loading support shows not the aes engine. My openssl version is #openssl version OpenSSL 1.0.1 14 Mar 2012 Can someone give me a hint what I am doing wrong. Regards, Torland

3 4

Unnamed flag
by kupo＠damnfbi.tk 15 Aug '12

15 Aug '12

Can anyone explain how to get the Unnamed flag for my node changed over to Named? -kupo

4 3