Re: [tor-relays] Deciding where to put new Tor relays

After talking with APNIC/RIPE, it looks like that if we ask nicely we can get high-quality BGP-peering graphs for the entire Internet (not 100% complete, but it's the same data they use internally). Spend some time thinking about exactly what kinds of attacks we wish to harden against. Once we

Re: [tor-relays] Obfsproxy OSX help

Hi Tim On Tue, Sep 22, 2015, at 01:40 AM, Tim Wilson-Brown - teor wrote: > > > On 21 Sep 2015, at 19:59, Geoff Down wrote: > > > > Hi all, > > is anyone willing to talk me through getting Obfsproxy working on > > OSX10.4? I've got as far as Step 3 on > >

Re: [tor-relays] Obfsproxy OSX help

> On 21 Sep 2015, at 19:59, Geoff Down wrote: > > Hi all, > is anyone willing to talk me through getting Obfsproxy working on > OSX10.4? I've got as far as Step 3 on > https://www.torproject.org/projects/obfsproxy-instructions.html.en#instructions > but can't find the

Re: [tor-relays] Tor is starting without the -f /etc/tor/torrc option

> > On 21/09/2015 15:50, Sean Greenslade wrote: > > On Sun, Sep 20, 2015 at 09:05:21PM +0100, Tor Stuff wrote: > >> I am running tor on a new Ubuntu 14.04.3 LTS system. I have > >> restarted tor a couple of times with > >> > >> service tor restart > >> > >> I noticed when I start arm that it is

Re: [tor-relays] Obfsproxy OSX help

> On 22 Sep 2015, at 12:00, Geoff Down wrote: > > Hi Tim > > On Tue, Sep 22, 2015, at 01:40 AM, Tim Wilson-Brown - teor wrote: >> >>> On 21 Sep 2015, at 19:59, Geoff Down wrote: >>> >>> Hi all, >>> is anyone willing to talk me through getting

[tor-relays] Non-standard Bridge

Hello all, I'm trying to set up a Bridge/Client Tor instance with the following torrc: ControlPort 9051 ExitPolicy reject *:* HashedControlPassword Nickname ORListenAddress 0.0.0.0:9001 ORPort 80 BridgeRelay 1 ContactInfo Should this work as a bridge? Client functionality is fine (port 80

Re: [tor-relays] Non-standard Bridge

You've set 2 port numbers, 9001 and 80, to listen on. Pick one or the other. Also, set "SocksPort 0". On Monday, September 21, 2015 1:20pm, "Geoff Down" said: > Hello all, > I'm trying to set up a Bridge/Client Tor instance with the following > torrc: > >

[tor-relays] Fwd: WG: Tor is starting without the -f /etc/tor/torrc option

Weitergeleitete Nachricht Betreff: WG: [tor-relays] Tor is starting without the -f /etc/tor/torrc option Datum: Mon, 21 Sep 2015 18:38:36 +0200 (MEST) Von:brightsidedarks...@t-online.de An: tor-relays@lists.torproject.org Sorry, to dumb to handle Android Mail.

Re: [tor-relays] Tor is starting without the -f /etc/tor/torrc option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It normally uses /usr/bin/ On 21/09/2015 15:50, Sean Greenslade wrote: > On Sun, Sep 20, 2015 at 09:05:21PM +0100, Tor Stuff wrote: >> I am running tor on a new Ubuntu 14.04.3 LTS system. I have >> restarted tor a couple of times with >> >>

Re: [tor-relays] Tor is starting without the -f /etc/tor/torrc option

On Sun, Sep 20, 2015 at 09:05:21PM +0100, Tor Stuff wrote: > I am running tor on a new Ubuntu 14.04.3 LTS system. I have restarted tor a > couple of times with > > service tor restart > > I noticed when I start arm that it is telling me that > > The torrc differs from what tor's using. You

[tor-relays] Obfsproxy OSX help

Hi all, is anyone willing to talk me through getting Obfsproxy working on OSX10.4? I've got as far as Step 3 on https://www.torproject.org/projects/obfsproxy-instructions.html.en#instructions but can't find the Obfsproxy binary; and since I have no idea what 'pip' does, even though it reports the

Re: [tor-relays] Deciding where to put new Tor relays

Hi Virgil, It appears that vizAS detects connections between ASes when they are observed as adjacent on paths reported by Route Views [0]. When I construct AS-level routing maps (e.g. as in [1]), I combine Route Views data with the AS-level topology produced by CAIDA [2]. The CAIDA topology is

Re: [tor-relays] Non-standard Bridge

On Mon, Sep 21, 2015, at 06:59 PM, Steve Snyder wrote: > You've set 2 port numbers, 9001 and 80, to listen on. Pick one or the > other. One is the internal port on which Tor listens, the other is the one advertised to the outside world. The router forwards one to the other - this works fine

Re: [tor-relays] Fwd: WG: Tor is starting without the -f /etc/tor/torrc option

Yeah, you're right. If we ever meet not knowing we're us, imagine the guy looking like an eremite hippie would just really invite you to his favourite coffee shop. ;-) -Original-Nachricht- Betreff: Re: [tor-relays] Fwd: WG: Tor is starting without the -f /etc/tor/torrc

Re: [tor-relays] Non-standard Bridge

Sorry, it's me spamming again. If you chose to transparently proxify whatever, you should set your browser agent and id and plugin and fonts settings similar to tor browsers'. If you don't, your browser is easy to be uniquely identified and the more time goes on, the more likely you're linked to

Re: [tor-relays] Non-standard Bridge

Hey again, I have a similar setup and I think up-to-date-synopsis is ORPort 80 NoListen ORPort 0.0.0.0:9001 NoAdvertise A good start to avoid proxy circumventing software is here. Notice potential flaws mentioned there! You might want to just torify a certain user or a machine or everything in

Re: [tor-relays] Fwd: WG: Tor is starting without the -f /etc/tor/torrc option

Hi Christian I think you lost that cup of coffee! I did a bit more research since my posting and found the info I needed by doing 'man tor' on my Ubuntu 14.04.3 system. The tor man page says that tor looks for /etc/tor/torrc by default, or $HOME/.torrc if that file is not found. I only have an