tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

Linux CVE-2014-0196
by zwiebel＠quantentunnel.de 13 May '14

13 May '14

Hi I received a notice from a server provider to immediatly update/upgrade/reboot if I would use Debian. It's the CVE-2014-0196 issue. I did and it came up with Wheezy 3.2.57-3+deb7u1 which should be fine. How relevant is this issue? Felix ==========---------- - - - - - - - - - - ----------========== -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.22 (MingW32) mQENBFL/5VoBCAC8l2gGmuy2hZf866dDkwzOvMkyJlfnFZU6T5LWe4uPIx0a8R1U cmj/Vut2yUCaJgvFpdOVA3mmXC58zoDeiW7Um6q6otD6BR2hXdgyBTAgqkQ0BsYx epb4UXBz/u3TJmv655fBnXeDgCB8L5BIkcsmX6EoBNUs6a3TPMhX3UXOtEKLXJeZ 2QtoDxwXqHNSmW7jLq+qkpriVDqxDTFv+muZRE+Zn/6PZpEASvpSdVdT/1giEMUL QQFIP6cBPY2GYIaNCO1dYRj9ebM7ewWjCiOiOw6/eylxan8vfFntgaPU3J7W2wJp RiRtUIjT+TDycVyNk7gy4wV2Rj8+58+Krk1tABEBAAG0IEZlbGl4IDx6d2llYmVs QHF1YW50ZW50dW5uZWwuZGU+iQE5BBMBAgAjBQJS/+VaAhsPBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4AACgkQC2jb92rYqyMGxQf/d9oJf0qpgXZaUmcqujQ3DVsc uvYOnK2MJCpDIvvZYdQTcnG2jz8/na1ZyfAGeKhYZ18ypONwSQYthC17L5GHQ2H3 Pg/H0GARtx4aJR5TtIKnhPR8yYdlikCuTBb5QSFJUUtEz91SqDW7EXNbMC4RRSEd BWWirADCJWitoR3JCC13r+CF6TCFDluClAht/t56f7prBzARVYWmlbgYD2yx4Uzs FOl0vvhW2o9dpVaLZ6mSHAyNzefCFcNumRUxqa+V6nY94dd8BV8xH0lOd1xaMtZW HuxIU9Sbh13OlJyBAvVffVBL+4sEOpc8XB6Yl/pmyjEjUSvC7lP3T+Ix9Mnk/A== =kfXw -----END PGP PUBLIC KEY BLOCK-----

2 2

Tor bridges on borrowed ports
by kzhm＠mailtor.net 09 May '14

09 May '14

Hello, assuming I have a friend, Bob. He has two IP addresses and wants to contribute to the tor network. He doesn't want to operate an exit, relay or bridge himself, though. I offer him to operate the bridges on my hardware and he's magically forwarding the required ports from his machines IPs to my machine so I do the relaying part of the bridging game. Bridge users benefit from the additional IP addresses that have to be blacklisted. I'm looking for a way to implement this. I could only think of *) inetd + nc *) dark iptables nat magic *) some sort of ip-over-ip tunnels which would all be kind of hacky, require installation of addition software and would probably have sideeffects on tors bridge stats. Can I announce an address that isn't directly mine? Can I use my address for outbound traffic to the next relay or do I need to use the "bridge address" for that? Is there a flaw in there? Is somebody already doing that? I'm putting this up for discussion. If I can get this working for Bob I could probably get access to some subnets from Charlie and Dave.. Waiting for input. Truly yours, Alice.

2 3

About running an Exit node
by Pika ohc 08 May '14

08 May '14

Hi there, I was considering to run an Exit node with my own pc, however, i have some questions about exit node. 1. How can I know if there is a client specifying me as an exit node and the traffic is sent from the client to me directly(where my exit node is the first node and also the last node for the client.)? 2. If i found some clients trying to do something bad by using the method mentiond in 1., how can I stop him? Is iptables or anything else can help me to block such clients? Hope there's someone can answer me. Thank you!

6 6

Mac OSX 10.6, re-installed, TBB downloaded, installed?, terminal window....what now?
by Robert Smith 08 May '14

08 May '14

I am NOT a Unix user. Decades ago, I was very skilled on an Amiga computer (I heard Amiga DOS was basically Linux). I have almost no experience on Macs. I hate them. My first attempt at installing Vidalia gave me a message saying: "You can't run Tor Browser with FireFox running". All programs that appeared in the "startup list" were unchecked (FireFox was not among them). Then after a cold boot, I got the same message. So I wiped the F##@$ Mac and re-installed only the OS (Snow Leopard) then updated it to the latest, 10.6 17. Then I download TBB again. Again I got just a terminal window. I tried to download and install the GUI version so I could get a simple bridge or relay running, but it looks the the terminal window is all I am going to get. If someone could post a link where I could download and install software for running a Tor relay or bridge, I'd appreciate it. Most computer users of my age are not nearly as experienced as I am. All lot younger than me, and they may not have the resources or interest to run a Tor relay. If it's hard to run relay or bridge on the most dumbed down OS (Macs seem very stable, but frustrating in anything I have attempted), who is going to be running relays? The 0.1% of the people out there. Mostly Linux experts and no one else. I'd run in on one of my PC's for now, but life is not allowing me the time, to make that an option at this time. Thanks for any advice.

2 1

Re: [tor-relays] Trying Trusted Tor Traceroutes
by starlight.2014q2＠binnacle.cx 08 May '14

08 May '14

At 22:35 5/7/2014 -0500, Anupam Das wrote: >Those are not our machines and moreover, we have not received any measurement (i.e., traceroute data) from those IPs. One more thing our traceroutes use UDP packets, not TCP packets. Thank you for your reply. I blocked the IPs.

1 0

Re: [tor-relays] Trying Trusted Tor Traceroutes
by starlight.2014q2＠binnacle.cx 08 May '14

08 May '14

forgot log entries

2 1

Re: [tor-relays] Trying Trusted Tor Traceroutes
by starlight.2014q2＠binnacle.cx 08 May '14

08 May '14

>Dear list members, > >Just a quick update regarding the TTTT >project. There are multiple GB's of data to >analyse and it is still being worked on. We are >also working on the public script(s) as well. > >Sebastian Urbach Have been seeing some dubious traffic warnings the last few days on the firewall from 50.116.9.77, 74.207.228.161 and 109.74.204.217. Are these IPs performing traceroutes for your project and can you vouch for them? If so will it improve your results if the ICMP TTL-expired packets are permitted? You should avoid the duplicate TCP SYNs if you don't want to annoy people. Maybe explain exactly (and tersely) how this works. If they're not yours they go on the black-hole ACL never to be seen again.

1 0

(no subject)
by I 07 May '14

07 May '14

4 4

SSH scans from Tor exit
by I 02 May '14

02 May '14

12 21

Relay down, "rejected", help
by kbesig 30 Apr '14

30 Apr '14

My relay became one of the "rejected" since the heartbleed vulnerability surfaced so I reformatted my XP relay and did a fresh Ubuntu 14.04 LTS install. Built vidalia-0.2.21 from source using: deb http://deb.torproject.org/torproject.org trusty main deb-src http://deb.torproject.org/torproject.org trusty main apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake apt-get build-dep vidalia mkdir ~/debian-packages; cd ~/debian-packages apt-get source vidalia cd vidalia-* debuild -rfakeroot -uc -us cd .. sudo dpkg -i vidalia_*.deb Edited /etc/tor/torrc allowing connection ports. I'm unable to open vidalia with these error messages: 1. As non-admin: /usr/bin/vidalia (process:540): GConf-WARNING **: Client failed to connect to the D-BUS daemon: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (<unknown>:540): GLib-GIO-ERROR **: No GSettings schemas are installed on the system Trace/breakpoint trap (core dumped) 2. As root: /usr/bin/vidalia No protocol specified vidalia: cannot connect to X server :0 3. As root: /usr/bin/X11/vidalia No protocol specified vidalia: cannot connect to X server :0 I've seen similar errors searching for a fix, but none that seemed "resolved". Any suggestions would be appreciated as I'd like to get back up and running ASAP Thanks ------------------------------------------------------------------------

15 23

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays