- tor-relays - lists.torproject.org

tornodeca is back
by cmeclax-sazri 17 Aug '11

17 Aug '11

There's only one now, in Canada, but it has the same nonexistent contact address my(a)mail.info as before, and again I got forwarding failure when my tor picked tornodeca as an exit for a website. cmeclax

1 0

Mitch McConnell
by Darrel 15 Aug '11

15 Aug '11

Well, nevermind. I do not need anonymity that badly- it is a thing of the past. Might as well be Japan defending nuclear power. Hi Mitch McConnell- ever smoke a joint? What is in the tea? Is it Republican? Do you have a fear of Kentuckians making money from plants? Commerce Man

1 0

exit node with private directory server
by Darrel 14 Aug '11

14 Aug '11

I have been reading the documentation and trying to get up to speed. Much of this is new to me. My goal is to have a directory server that is only available on my local-area network and on the same machine run an exit node available to the "onion network". Is this sort of configuration possible? I am installing a dedicated FreeBSD 9-beta computer at the moment and want to run run this configuration as my first tor installation. Darrel

1 0

directory and exit node on same server
by Darrel 14 Aug '11

14 Aug '11

I have been reading the documentation and trying to get up to speed. Much of this is new to me. My goal is to have a directory server that is only available on my local-area network and on the same machine run an exit node available to the "onion network". Is this sort of configuration possible? I am installing a dedicated FreeBSD 9-beta computer at the moment and want to run private directory and "public" exit node. Darrel

1 0

circuit ends in myself
by cmeclax-sazri 11 Aug '11

11 Aug '11

I just restarted tor after upgrading the version, then brought up Vidalia, and one of the circuits ends in myself! (xxx,xxx,cmeclax0 where the xxx's are other relays) How come? I'm a middleman.

2 2

Received abuse complaint - how did this happen?
by Steve Snyder 10 Aug '11

10 Aug '11

Today my ISP informed me that an abuse complaint had been lodged against me by spamcop.net. I looked at the report and my IP is indeed in it. It seems like a valid complaint. My question, though, is how did this happen? I'm using the Reduced Exit Policy as shown here: https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/ReducedExitPol… Neither SMTP nor SMTPS are among the ports accepted as exit ports. Anyone have any thoughts as to how my Tor config can be used to transmit spam? Thanks.

4 4

jumping clock
by Softail 09 Aug '11

09 Aug '11

Every few days I find a log message like this Aug 08 07:20:09.241 [warn] Your system clock just jumped 122 seconds forward; assuming established circuits no longer work. Seems to always be 122 seconds as far as I can tell and happens at random times. Doesn't seem to be correlated with the log rotations or anything else. I'm running ntpd and that seems to be working fine. I started to let it use the kludge local clock in case the network was unavailable. I didn't think that was likely and it doesn't seem to have made any difference. Google turns up some complaints about this on much older versions 2.0.23. I'm currently running 2.1.30 from the Tor repository. It's i386 running on x86_64. I suppose I could try rebuilding a 64 bit version but so far haven't built my own yet. Would eventually like to dig into the sources but don't have time right now. Anybody else see this or have suggestions about what to do about it? Thanks -- A man in chains knows he should have acted sooner... Julian Assange

3 4

Setting up a "hidden" exit node
by Joel Hobson 09 Aug '11

09 Aug '11

Hi all, I'm an undergraduate student working as a research assistant for the summer. My current task is to figure out a way to measure delay caused by individual nodes (we want to replicate this paper: http://cis.poly.edu/~ross/papers/Tor.pdf <http://cis.poly.edu/%7Eross/papers/Tor.pdf>). It seems to me that the easiest way of accomplishing this would be to run an exit node and construct a two-hop circuit to it. OP ------> Node to be measured -------> Exit node Since the OP and exit node are under my control, I could measure the time it takes for any packets to reach the exit node from the OP. I want to be the only one who can use this exit node so I don't have to worry about getting approval from the school to run an exit node (could be time-consuming). I realize this is pretty far from any design goals the developers have, but is there some way of running a hidden exit node? One that doesn't appear on any directory server (PublishServerDescriptor 0 might work)****, but can still be used if you know its IP address? The Tor Control Protocol makes it easy enough to create a custom circuit (discussed here: http://thesprawl.org/memdump/?entry=8) but it won't accept IP addresses for nodes. I can put an IP in exitnodes in the torrc file, but exitnodes doesn't seem to have any effect, even when StrictExitNodes is set. Thanks Joel

2 1

bb
by 向梁 06 Aug '11

06 Aug '11

bb

1 0

Newbie Messed up Relay Setup
by flgcrz 05 Aug '11

05 Aug '11

Hello, Is this the right place to post if I'm having difficulties? I've done quite a bit of searching forums and things. I'm new to this and have been struggling a bit to get Tor and Vidalia working smoothly. I think I know what the problem is . I had my relay setup and working fine but Tor was not working. So I looked around a bit and I found this post on the Ubuntu forums and a useful guide to setting up Tor Vidalia and Polipo. I followed the instructions in that guide and finally Tor is working both when Vidalia boots and in my browser albeit with Torbutton as opposed to Foxyproxy (recommended in the guide). I thought this is great progress finally. But no I messed something up. In my enthusiasm I had copied the torrc from the guide without backing up my original and now my relay is no longer working. There are I believe 2 issues. The first I think is that the original references to my keys have been deleted. The second is I think something to do with the setup I have for ControlPort. I don't think its a firewall issue. I am running a firewall locally and have port forwarding setup on my wireless router for 9001 and 9030 Like I said I'm new to all this so I could be wrong. I also don't know a lot about encryption so I am hesitant to post the details of my logs on a public list. I've messed things up so if this is too much of a pain is there a way to just wipe out old keys and start a new relay from scratch? Thanks you in advance Best Kevin ---- Here is the post on Ubuntu Forums http://ubuntuforums.org/showthread.php?p=11117515#post11117515 Here are some of the details from from my logs ( minus the encyption stuff which I can post if those who know better think its ok to do so) Aug 04 18:38:10.018 [Info] resolve_my_address(): Guessed local hostname 'CRZ' resolves to a private IP address (127.0.0.1). Trying something else. Aug 04 18:38:10.019 [Info] resolve_my_address(): Interface IP address '192.168.1.130' is a private address too. Ignoring. Aug 04 18:38:10.023 [Info] resolve_my_address(): Address 'CRZ' resolves to private IP address '127.0.0.1'. Tor servers that use the default DirServers must have public IP addresses. Aug 04 18:38:10.023 [Info] router_pick_published_address(): Could not determine our address locally. Checking if directory headers provide any hints. Aug 04 18:38:10.024 [Info] resolve_my_address(): Guessed local hostname 'CRZ' resolves to a private IP address (127.0.0.1). Trying something else. Aug 04 18:38:10.025 [Info] resolve_my_address(): Interface IP address '192.168.1.130' is a private address too. Ignoring. Aug 04 18:38:10.026 [Info] resolve_my_address(): Address 'CRZ' resolves to private IP address '127.0.0.1'. Tor servers that use the default DirServers must have public IP addresses. Aug 04 18:38:10.027 [Info] router_pick_published_address(): Could not determine our address locally. Checking if directory headers provide any hints. Aug 04 18:38:10.027 [Info] update_consensus_router_descriptor_downloads(): 0 router descriptors downloadable. 0 delayed; 2494 present (0 of those were in old_routers); 0 would_reject; 0 wouldnt_use; 0 in progress. Aug 04 18:38:10.028 [Info] resolve_my_address(): Guessed local hostname 'CRZ' resolves to a private IP address (127.0.0.1). Trying something else. Aug 04 18:38:10.029 [Info] resolve_my_address(): Interface IP address '192.168.1.130' is a private address too. Ignoring. Aug 04 18:38:10.030 [Info] resolve_my_address(): Address 'CRZ' resolves to private IP address '127.0.0.1'. Tor servers that use the default DirServers must have public IP addresses. Aug 04 18:38:10.030 [Info] router_pick_published_address(): Could not determine our address locally. Checking if directory headers provide any hints. Aug 04 18:38:10.031 [Info] routerlist_remove_old_routers(): We have 2617 live routers and 1253 old router descriptors. Aug 04 18:38:10.032 [Info] resolve_my_address(): Guessed local hostname 'CRZ' resolves to a private IP address (127.0.0.1). Trying something else.

2 1