On 08/28/2016 04:26 PM, Petrusko wrote:
>
>> Up to two per IP.
> Hu? it's sad for people having several CPU... :s
>
It does help a little to prevent attackers from spinning up a lot of
relays. With this limit, they must have n/2 IPs at their disposal.
For example, this paper[1] shows an attac
> Up to two per IP.
Hu? it's sad for people having several CPU... :s
--
Petrusko
PubKey EBE23AE5
C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.tor
On 08/28/2016 04:18 PM, Petrusko wrote:
> Hey,
> Tor process is only mono-cpu, so if you have RPi v2 or v3, the full quad
> core will not be used 100% by 1 Tor process.
Tor is mostly 1 process, but it does now do crypto on a separate thread.
> On this list I've already read it's possible to lau
Hey,
Tor process is only mono-cpu, so if you have RPi v2 or v3, the full quad
core will not be used 100% by 1 Tor process.
On this list I've already read it's possible to launch several Tor
processes, so all cpu x4 cores can be used at same time.
About hardware, I don't know if the RPi can go to 2
Hi Daniel,
Judging from my pi3 mid relay where 5mbit traffic is
about 20% of 1 core (tor uses 1 core mostly) 20-25mbit should be fine for pi3.
In the peak hours it will be probably close to maximum what pi3 is capable on 1
core
but when cost is a factor I would not think of anything else
1gb ram
On 26/08/2016 14:37, Toralf Förster wrote:
> On 08/25/2016 07:02 PM, Toralf Förster wrote:
>> This is a fresh new Tor exit, setup 4 days ago,
>> https://atlas.torproject.org/#details/BE2FA9FCB6242567B93ED99FEC5543FC517C9276
>> , where I do wonder how to interpret the attached screen shot.
>
> Th
