Re: [tor-relays] interpreting extra-infos

eliaz transcribed 0.4K bytes: > Can anyone point me to a tutorial about how to read the extra-info > output of CollecTor? I'm particularly interested in what > bridge-ip-versions v4=0,v6=0 means and why bridge-ip-transports does not > report the the pluggable transport proxies (obfs3, obfs4,

[tor-relays] interpreting extra-infos

Can anyone point me to a tutorial about how to read the extra-info output of CollecTor? I'm particularly interested in what bridge-ip-versions v4=0,v6=0 means and why bridge-ip-transports does not report the the pluggable transport proxies (obfs3, obfs4, etc.) for the bridge I'm running.

Re: [tor-relays] Exit relay seized by police

On Tue, Nov 10, 2015 at 12:40:19AM +, Tim Sammut wrote: > I meant is it possible for a relay operator to detect if a snapshot of a > running VM or VPS has been taken? Asked slightly differently, if I have > a relay running as a VPS or VM, can I somehow detect if my provider took > a snapshot

[tor-relays] TorFlow

A gorgeous visualization of the Tor's data traffic. Feast your eyes! https://torflow.uncharted.software/ 0xDD79757F.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list

Re: [tor-relays] TorFlow

Oooh, very neat! Just a quick head's up about an unfortunately naming conflict... https://gitweb.torproject.org/torflow.git/ TorFlow is the name of the codebase that backs the Directory Authorities. That said, the library's obviously not user facing and will likely go away when the DirAuths get

Re: [tor-relays] Exit relay seized by police

Hi Tim, sorry. On 11/10/2015 12:33 AM, Tim Wilson-Brown - teor wrote: >> On 11/06/2015 08:41 PM, Tim Wilson-Brown - teor wrote: > The directory authorities are generally more concerned when > they *don't* stop it afterwards, and instead keep running it, > perhaps with extra logging,

Re: [tor-relays] Exit relay seized by police

Hi Tim, everyone. On 11/06/2015 08:41 PM, Tim Wilson-Brown - teor wrote: > The directory authorities are generally more concerned when they > *don't* stop it afterwards, and instead keep running it, perhaps with > extra logging, packet dumps, and decryption via seized private keys. Is there a

Re: [tor-relays] TorFlow

> On 10 Nov 2015, at 11:05, I wrote: > > That is very nice and gives an idea of the need for more geographical > diversity. > > Do you have an idea why there is almost no activity visible from Australia > and none from New Zealand? International bandwidth is very

Re: [tor-relays] Exit relay seized by police

> On 10 Nov 2015, at 11:28, Tim Sammut wrote: > > Hi Tim, everyone. > > On 11/06/2015 08:41 PM, Tim Wilson-Brown - teor wrote: >> The directory authorities are generally more concerned when they >> *don't* stop it afterwards, and instead keep running it, perhaps with >>

Re: [tor-relays] Faravahar messing with my IP address

> On 9 Nov 2015, at 18:56, Matthew Finkel wrote: > > Which version of Tor were you previously running? Have you seen these > messages within the last few days, after you upgraded? > Hi SiNA, Matthew, I can reproduce some unusual behaviour from Faravahar simply using

Re: [tor-relays] Faravahar messing with my IP address

On Mon, Nov 09, 2015 at 08:04:55PM +1100, Tim Wilson-Brown - teor wrote: > Subsequent queries get the same IP address for several tens of seconds > afterwards. Woah. Are we setting the Expires: http header in our Tor answer based on how long we think the *payload* will remain valid, and the

Re: [tor-relays] Faravahar messing with my IP address

On Sat, Oct 24, 2015 at 03:09:00AM +0300, s7r wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello, > > Unfortunately this is not the first time we see this, and it did > happen before Faravahar IP address change and before it was > experiencing very high latency ( >

Re: [tor-relays] Wrong IP from faravahar again

On Mon, Nov 09, 2015 at 06:34:21AM +, Pascal Terjan wrote: > Nov 04 17:06:00.000 [notice] Our IP Address has changed from > 149.18.2.82 to 154.35.32.5; rebuilding descriptor (source: > 154.35.175.225). > Nov 04 17:08:55.000 [notice] Our IP Address has changed from > 154.35.32.5 to 149.18.2.82;

Re: [tor-relays] Faravahar messing with my IP address

On 9 Nov 2015, at 20:45, Roger Dingledine > wrote: > On Mon, Nov 09, 2015 at 08:04:55PM +1100, Tim Wilson-Brown - teor wrote: >> Subsequent queries get the same IP address for several tens of seconds >> afterwards. > > Woah. Are we setting the Expires: http