Re: is tor an email mixmaster?
* on the Sun, Nov 09, 2008 at 10:43:29AM -0800, Christopher Davis wrote: someone has setup an open SMTP relay as hidden service: oogjrxidhkttf6vl.onionport: 587 May be, it works. I did not test it. :-( Unfortunately, this doesn't seem to be running. The idea is interesting, though. It would be prudent to enable spam filtering and/or hashcash for a service like this, of course. Yeah. I've heared that relay mentioned several times before, but I've never been able to connect to it. I can connect to other hidden services fine. You're the first other person I've come across that has either confirmed it working or not working. -- Erilenz
Problems runing Tor on Vista x64
Hi I tried to run Tor on my Vista Ultimate x64 but for some reason
cant get it started only messages I get are as follows
Nov 10 09:34:42.387 [notice] Tor v0.2.0.31 (r16744). This is
experimental software. Do not rely on it for strong anonymity.
(Running on Windows Longhorn Service Pack 1 [workstation] {terminal
services, single user})
Nov 10 09:34:42.445 [err] Error from libevent: evsignal_init:
socketpair: No error
Same problem with latest stable and alpha.
No mater what I type on commandline or put into torrc result is always the same.
Tried runing it with elevated (admin) privileges and with standart
user privileges no difference.
Any sugestions would be welcome
Dir servers on private networks
Hey everyone, Our research team is a bit stuck on a problem of bootstrapping generic Tor on a private network in planetlab. The two authoritative directory servers that we are running continuously complain that, Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all again. Nov 10 12:22:35.487 [info] directory_get_from_dirserver(): No router found for consensus network-status fetch; falling back to dirserver list. Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [notice] While fetching directory info, no running dirservers known. Will try again later. (purpose 14) However, OR's in the network seem to think that they are publishing their descriptors without any problem. When we attempt to browse to http://[host]:[port]/all into the Dir port of either of the two authoritative dir servers, it consistently responds with zero content - we are assuming this is why clients are OR's are not yet communicating with each other. We've attempted this setup on both V1 and V2 dir servers. We have exhausted the specific guidance for running a private Tor network found here: http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#OwnTorNetwork Any comments, suggestions, ideas, or guidance would be most appreciated. :) ~Jon
RE: Dir servers on private networks
Did you put the info about your authoritative directory servers into config.c? You may need to run the them first to generate the fingerprints. Have you looked at the IP addresses your ORs are publishing to? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon McLachlan Sent: Monday, November 10, 2008 9:36 AM To: or-talk@freehaven.net Subject: Dir servers on private networks Hey everyone, Our research team is a bit stuck on a problem of bootstrapping generic Tor on a private network in planetlab. The two authoritative directory servers that we are running continuously complain that, Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all again. Nov 10 12:22:35.487 [info] directory_get_from_dirserver(): No router found for consensus network-status fetch; falling back to dirserver list. Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [notice] While fetching directory info, no running dirservers known. Will try again later. (purpose 14) However, OR's in the network seem to think that they are publishing their descriptors without any problem. When we attempt to browse to http://[host]:[port]/all into the Dir port of either of the two authoritative dir servers, it consistently responds with zero content - we are assuming this is why clients are OR's are not yet communicating with each other. We've attempted this setup on both V1 and V2 dir servers. We have exhausted the specific guidance for running a private Tor network found here: http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#OwnTorNetwork Any comments, suggestions, ideas, or guidance would be most appreciated. :) ~Jon
Re: Dir servers on private networks
We didn't put the info into the config.c list of auth. dir servers, because it seems like the torrc options regarding Dirserver will override the hardcoded entries. Perhaps this is a false assumption? ~Jon On Nov 10, 2008, at 2:22 PM, Steve Southam wrote: Did you put the info about your authoritative directory servers into config.c? You may need to run the them first to generate the fingerprints. Have you looked at the IP addresses your ORs are publishing to? -Original Message- From: [EMAIL PROTECTED] [mailto:owner-or- [EMAIL PROTECTED] On Behalf Of Jon McLachlan Sent: Monday, November 10, 2008 9:36 AM To: or-talk@freehaven.net Subject: Dir servers on private networks Hey everyone, Our research team is a bit stuck on a problem of bootstrapping generic Tor on a private network in planetlab. The two authoritative directory servers that we are running continuously complain that, Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all again. Nov 10 12:22:35.487 [info] directory_get_from_dirserver(): No router found for consensus network-status fetch; falling back to dirserver list. Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [notice] While fetching directory info, no running dirservers known. Will try again later. (purpose 14) However, OR's in the network seem to think that they are publishing their descriptors without any problem. When we attempt to browse to http://[host]:[port]/all into the Dir port of either of the two authoritative dir servers, it consistently responds with zero content - we are assuming this is why clients are OR's are not yet communicating with each other. We've attempted this setup on both V1 and V2 dir servers. We have exhausted the specific guidance for running a private Tor network found here: http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#OwnTorNetwork Any comments, suggestions, ideas, or guidance would be most appreciated. :) ~Jon
problems with 0.2.1.7-alpha
When I build and install the latest 0.2.1.7-alpha tor, it refuses to run: Nov 10 15:30:25.383 [notice] Tor v0.2.1.6-alpha (r17011). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Nov 10 15:30:25.385 [warn] Failed to parse/validate config: Servers must be able to freely connect to the rest of the Internet, so they must not set Reachable*Addresses or FascistFirewall. Nov 10 15:30:25.385 [err] Reading config failed--see warnings above. When I go back to 0.2.1.6-alpha, it works fine. What has changed in the latest to break it in this fashion? Is there some new magical setting that needs to be made in the config?
Re: Dir servers on private networks
OR's are definitely posing their descriptors to the Dir, and the dir is collecting them, voting on them (V3), and publishing lists of them to http://[dirserver]:[dirport]/tor/server/all At the same time as the above statement is true, router descriptors are not being shared, as this dir log msg suggests: Nov 10 14:39:25.176 [info] update_consensus_router_descriptor_downloads(): 0 router descriptors downloadable. 0 delayed; 0 present (0 of those were in old_routers); 0 would_reject; 0 wouldnt_use; 0 in progress. Maybe there is a way to force downloadablility of OR descriptors on dir servers instantly? ~Jon On Nov 10, 2008, at 11:36 AM, Jon McLachlan wrote: Hey everyone, Our research team is a bit stuck on a problem of bootstrapping generic Tor on a private network in planetlab. The two authoritative directory servers that we are running continuously complain that, Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all again. Nov 10 12:22:35.487 [info] directory_get_from_dirserver(): No router found for consensus network-status fetch; falling back to dirserver list. Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [notice] While fetching directory info, no running dirservers known. Will try again later. (purpose 14) However, OR's in the network seem to think that they are publishing their descriptors without any problem. When we attempt to browse to http://[host]:[port]/all into the Dir port of either of the two authoritative dir servers, it consistently responds with zero content - we are assuming this is why clients are OR's are not yet communicating with each other. We've attempted this setup on both V1 and V2 dir servers. We have exhausted the specific guidance for running a private Tor network found here: http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#OwnTorNetwork Any comments, suggestions, ideas, or guidance would be most appreciated. :) ~Jon
Re: Dir servers on private networks
On Mon, Nov 10, 2008 at 02:40:07PM -0600, Jon McLachlan wrote:
Maybe there is a way to force downloadablility of OR descriptors on
dir servers instantly?
Check out the TestingTorNetwork config option in 0.2.1.x-alpha. It's
not quite instantly, but it turns on a lot of config options that make
it smoother to run your own network:
static config_var_t testing_tor_network_defaults[] = {
V(ServerDNSAllowBrokenResolvConf, BOOL, 1),
V(DirAllowPrivateAddresses,BOOL, 1),
V(EnforceDistinctSubnets, BOOL, 0),
V(AssumeReachable, BOOL, 1),
V(AuthDirMaxServersPerAddr,UINT, 0),
V(AuthDirMaxServersPerAuthAddr,UINT, 0),
V(ClientDNSRejectInternalAddresses, BOOL,0),
V(ExitPolicyRejectPrivate, BOOL, 0),
V(V3AuthVotingInterval,INTERVAL, 5 minutes),
V(V3AuthVoteDelay, INTERVAL, 20 seconds),
V(V3AuthDistDelay, INTERVAL, 20 seconds),
V(TestingV3AuthInitialVotingInterval, INTERVAL, 5 minutes),
V(TestingV3AuthInitialVoteDelay, INTERVAL, 20 seconds),
V(TestingV3AuthInitialDistDelay, INTERVAL, 20 seconds),
V(TestingAuthDirTimeToLearnReachability, INTERVAL, 0 minutes),
V(TestingEstimatedDescriptorPropagationTime, INTERVAL, 0 minutes),
You'll still need to set your own DirServer lines.
If you continue to have problems, you should put your torrc files up
somewhere. Giving us ambiguous warning messages without hints about what
config options are set doesn't give us enough info. :)
--Roger
Re: problems with 0.2.1.7-alpha
On Mon, Nov 10, 2008 at 03:38:01PM -0500, [EMAIL PROTECTED] wrote 0.7K bytes in 12 lines about: : When I build and install the latest 0.2.1.7-alpha tor, it refuses to run: : : Nov 10 15:30:25.383 [notice] Tor v0.2.1.6-alpha (r17011). This is experimental : software. Do not rely on it for strong anonymity. (Running on Linux i686) You aren't running 0.2.1.7-alpha here. -- Andrew
Re: problems with 0.2.1.7-alpha
On Monday 10 November 2008 16:48:46 [EMAIL PROTECTED] wrote: On Mon, Nov 10, 2008 at 03:38:01PM -0500, [EMAIL PROTECTED] wrote 0.7K bytes in 12 lines about: : When I build and install the latest 0.2.1.7-alpha tor, it refuses to run: : : Nov 10 15:30:25.383 [notice] Tor v0.2.1.6-alpha (r17011). This is : experimental software. Do not rely on it for strong anonymity. (Running : on Linux i686) You aren't running 0.2.1.7-alpha here. Oops. I got this after trying to run 0.2.1.7-alpha and getting the same output, then I went back to 0.2.1.6-alpha but didn't go through the tork wizard process to set up tor, so I got the same thing with 0.2.1.6-alpha. Upon re-running the setup wizard, tor-0.2.1.6-alpha (unlike 0.2.1.7-alpha) worked fine...but I am nervous about running this one because of the problems I was having over the last week with RAM and CPU consumption. praedor
Re: Dir servers on private networks
A few months back I ran into the same problem. I ended up using V3 dir servers. On Nov 10, 2008, at 12:36 PM, Jon McLachlan wrote: Hey everyone, Our research team is a bit stuck on a problem of bootstrapping generic Tor on a private network in planetlab. The two authoritative directory servers that we are running continuously complain that, Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all again. Nov 10 12:22:35.487 [info] directory_get_from_dirserver(): No router found for consensus network-status fetch; falling back to dirserver list. Nov 10 12:22:35.487 [info] router_pick_trusteddirserver(): No trusted dirservers are reachable. Trying them all again. Nov 10 12:22:35.487 [notice] While fetching directory info, no running dirservers known. Will try again later. (purpose 14) However, OR's in the network seem to think that they are publishing their descriptors without any problem. When we attempt to browse to http://[host]:[port]/all into the Dir port of either of the two authoritative dir servers, it consistently responds with zero content - we are assuming this is why clients are OR's are not yet communicating with each other. We've attempted this setup on both V1 and V2 dir servers. We have exhausted the specific guidance for running a private Tor network found here: http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#OwnTorNetwork Any comments, suggestions, ideas, or guidance would be most appreciated. :) ~Jon
Version deprecated?
This is new in the last day or so: 'Nov 10 16:24:16.973 [Notice] This version of Tor (0.2.0.31) is newer than any recommended version in its series, according to the directory authorities. Recommended versions are: 0.1.2.17,0.1.2.18,0.1.2.19,0.2.0.26-rc,0.2.0.27-rc,0.2.0.28-rc,0.2.1.1- alpha,0.2.1.2-alpha,0.2.1.4-alpha,0.2.1.5-alpha,0.2.1.6-alpha,0.2.1.7- alpha ' Since I got it in the Vidalia/Privoxy/Tor bundle, this seems odd. The version at https://www.torproject.org/download.html.en hasn't changed GD
Re: Version deprecated?
On Tue, Nov 11, 2008 at 04:01:22AM +, Geoff Down wrote: This is new in the last day or so: 'Nov 10 16:24:16.973 [Notice] This version of Tor (0.2.0.31) is newer than any recommended version in its series, according to the directory authorities. Recommended versions are: 0.1.2.17,0.1.2.18,0.1.2.19,0.2.0.26-rc,0.2.0.27-rc,0.2.0.28-rc,0.2.1.1- alpha,0.2.1.2-alpha,0.2.1.4-alpha,0.2.1.5-alpha,0.2.1.6-alpha,0.2.1.7- alpha ' Looks like gabelmoo isn't recommending quite the set of versions it should be recommending. That is, it's missing 0.2.0.29-rc, 0.2.0.30, 0.2.0.31. Since moria1 and tor26 do recommend those, the majority rules, so you will get the correct recommendations most of the time. But I suppose if a consensus gets built that's missing moria1 or tor26, then the majority of versioning authorities would no longer recommend 0.2.0.31. Hopefully Karsten will fix his authority soon. Thanks! --Roger
Re: problems with 0.2.1.7-alpha
On Mon, Nov 10, 2008 at 05:01:23PM -0500, [EMAIL PROTECTED] wrote 0.9K bytes in 19 lines about: : Upon re-running the setup wizard, tor-0.2.1.6-alpha (unlike 0.2.1.7-alpha) : worked fine...but I am nervous about running this one because of the problems : I was having over the last week with RAM and CPU consumption. I wonder if tork is doing something odd with the config options. The minimum you have to configure for a relay is: https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#CanIJustConfigureAndRun. -- Andrew
Re: Problems runing Tor on Vista x64
On Mon, Nov 10, 2008 at 09:51:00AM +0100, [EMAIL PROTECTED] wrote 0.7K bytes in 16 lines about: : Nov 10 09:34:42.445 [err] Error from libevent: evsignal_init: : socketpair: No error It reads like libevent doesn't like something in the wow32 subsystem inside 64-bit vista. Do you get a drwatson crash dump? -- Andrew
Re: Problems runing Tor on Vista x64
[EMAIL PROTECTED] wrote: On Mon, Nov 10, 2008 at 09:51:00AM +0100, [EMAIL PROTECTED] wrote 0.7K bytes in 16 lines about: : Nov 10 09:34:42.445 [err] Error from libevent: evsignal_init: : socketpair: No error It reads like libevent doesn't like something in the wow32 subsystem inside 64-bit vista. Do you get a drwatson crash dump? The venerable Dr. Watson chose to enter well-deserved retirement with the release of Vista. The good doctor's successor is WinDbg. Both 64-bit and 32-bit versions can be found at: http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx Users of Windows XP, 2000, and even NT4 are equally encouraged to let the good doctor rest by installing the tools found at the above URL. Enjoy, --Lucky
