Hi,
On 17/09/17 04:56, Iain R. Learmonth wrote:
> I'll have a think about this.
I had a little think about this. While the search strategy is something
to consider, I've hacked up a simple tool for building circuits and
detecting, at a very high level, when it fails. I don't yet have the
reason f
dawuud:
> In
> fact, the network is *very* partitioned... but as of the past few
> months I haven't put any energy into proving this; although I do have
> some mostly finished twisted python code to make all two hop tor
> circuits and records circuit build failures and circuit build timeouts.
teor
One must take care in the design of such Tor network scanning tools
to not make successive circuits through the same relays repeatedly.
Instead relay pairs should be shuffled.
Yes AND if circuit building A->B fails but B->A succeeds then a
subsequent A->B should also succeed.
On Sun, Sep 17, 2
> This is a great research area that it would be good to see some
> attention for.
Alrighty... I will try to find time to resume work on this soon. I'm
hoping Meejah or Jean-Paul will help me with this. I've always thought
this would be a fun project to do for Tor and now that you've
expressed in
I think it's good that there's a few tools to do this so we can
compare notes, but I'm going to use the tool I wrote since it has
resume functionality AND a partitioning scheme such that multiple
workers (perhaps on different machines) can in parallel scan the tor
network. It uses the Fisher Yates
Hi
I'm running an obfs4 bridge and upgraded to latest version.
Use Debian Jessie (8.9).
One thing that puzzles me is the log
/var/log/tor/log
I used to always see some useful info there, like number of connecting clients
during the last 6 hours etc.
I have an entry:
[notice] Clean shutdown fi
Hello list,
I was hoping to get a good suggestion from here for a hosting provider
that is tolerant with Tor exit nodes.
I went through the mailing list archive a few months back and there
weren't any good suggestions on hosting providers.
Also, I checked the 'GoodBadISPs' page in the Tor w
> I am not sure who edits and keeps track of the mentioned page but it
> would be a good idea to remove the mentioned provider from there so
> other people wont waste their money.
trac.torproject.org is a wiki, everyone can edit it.
I moved the hoster you mentioned to the 'bad' section.
--
http
Hi folks,
I'm running a few relays on CentOS 7
As I'm sticking to the ease of rpm distributions, I'm left behind on
0.2.9.10 from EPEL
Does anyone know of another rpm repository with a more up to date version ?
Thanks!
Patrick
___
tor-relays mailing l
> I'm running a few relays on CentOS 7
> As I'm sticking to the ease of rpm distributions, I'm left behind on
> 0.2.9.10 from EPEL
>
> Does anyone know of another rpm repository with a more up to date version ?
I'm not aware of any updated (trustworthy) RPM repository.
Also the promising comment
On Sun, Sep 17, 2017 at 8:22 AM, nusenu wrote:
>> I'm running a few relays on CentOS 7
>> As I'm sticking to the ease of rpm distributions, I'm left behind on
>> 0.2.9.10 from EPEL
>>
>> Does anyone know of another rpm repository with a more up to date version ?
>
> I'm not aware of any updated (t
http://lmgtfy.com/?q=CVE-2017-0380
> Original Message
> Subject: Re: [tor-relays] More recent rpm somewhere?
> Local Time: September 17, 2017 12:53 PM
> UTC Time: September 17, 2017 12:53 PM
> From: bnag...@gmail.com
> To: tor-relays@lists.torproject.org
>
> On Sun, Sep 17, 2017
>> The upcoming tor releases fixing CVE-2017-0380 will make it even more
>> uncomfortable for RPM users if there will be no updated packages for
>> them and it does not look like there is anyone working on it.
>
> Can you provide a reference to CVE-2017-0380, please?
https://trac.torproject.org/p
Roger Dingledine wrote:
> On Sat, Sep 16, 2017 at 11:44:41PM +, dawuud wrote:
> > > Your only option would be to ask your ISP to uncensor the internet,
> > > unfortunately. Tor requires that all relays are able to contact all
> > > other relays, and those which cannot participate in the netwo
https://box.cock.li FTW
yeah it's servers with cocks, but it is in Romania / IP location the
Seychelles, and I have had no issues with my exit node on them.
Sunday, September 17, 2017, 11:32:33 AM, you wrote:
> Hello list,
> I was hoping to get a good suggestion from here for a hosting provid
https://okservers.net/ is newer, but they are Tor friendly, very price
competitive, and allow payment in Bitcoin.
On Sun, Sep 17, 2017 at 1:59 PM King Queen wrote:
> https://box.cock.li FTW
>
> yeah it's servers with cocks, but it is in Romania / IP location the
> Seychelles, and I have had no i
Alec Larsen:
> https://okservers.net/ is newer, but they are Tor friendly, very price
> competitive, and allow payment in Bitcoin.
I see you added your exit relay very recently.
This interesting AS appeared already before on this list:
https://lists.torproject.org/pipermail/tor-relays/2017-May/
Alec Larsen:
> https://okservers.net/ is newer, but they are Tor friendly, very price
> competitive, and allow payment in Bitcoin.
That AS hosts already >2.5% exit probability (position #8 on the biggest
exit ASes) because it hosts the fastest exit.
https://atlas.torproject.org/#search/as:AS395
nusenu:
>
>
> Alec Larsen:
>> https://okservers.net/ is newer, but they are Tor friendly, very price
>> competitive, and allow payment in Bitcoin.
>
>
> That AS hosts already >2.5% exit probability (position #8 on the biggest
> exit ASes) because it hosts the fastest exit.
> https://atlas.torpr
>
> On 17 Sep 2017, at 17:11, Iain R. Learmonth wrote:
>
> The most interesting thing I've discovered so far is that it's common
> for the connections to fail in one direction but then succeed when the
> two relays are reversed. I can't be sure if this is because I can't
> reach one of the relay
Am 17.09.2017 01:56 schrieb Roger Dingledine:
On Sat, Sep 16, 2017 at 11:44:41PM +, dawuud wrote:
> Your only option would be to ask your ISP to uncensor the internet,
> unfortunately. Tor requires that all relays are able to contact all
> other relays, and those which cannot participate in
21 matches
Mail list logo
