Hello,
i wanted to share the experience in running a Tor Relay (no-exit) on a
small embedded computer costing 7eur/month at oneprovider with unlimited
1Gbps bandwidth (at least they say that):
VIA Nano processor U2250 (1.6GHz Capable)
2GB Ram
I had to install to get the hw acceleration library:
On Sun, 5 Jun 2016 13:28:04 +0200
"Fabio Pietrosanti (naif) - lists" wrote:
> I had to install to get the hw acceleration library:
> Tor version 0.2.8.1-alpha (git-9093e3769746742f).
Which OS do you use?
In my experience I had to recompile OpenSSL with the Padlock patch:
https://romanrm.net/ope
On 6/5/16 2:17 PM, Roman Mamedov wrote:
> On Sun, 5 Jun 2016 13:28:04 +0200
> "Fabio Pietrosanti (naif) - lists" wrote:
>
>> I had to install to get the hw acceleration library:
>> Tor version 0.2.8.1-alpha (git-9093e3769746742f).
>
> Which OS do you use?
>
> In my experience I had to recompi
On 6/5/16 5:01 PM, Fabio Pietrosanti (naif) - lists wrote:
>> Do you get messages about successfully using 'padlock' in /var/log/tor/log?
> Yes
> root@dedi-fr-23644:~# zgrep -i padlock /var/log/tor/log*
> /var/log/tor/log:Jun 05 16:58:27.000 [notice] Default OpenSSL engine for
> AES-128-ECB is V
On Sun, 5 Jun 2016 17:01:29 +0200
"Fabio Pietrosanti (naif) - lists" wrote:
> > Do you mean 60 Mbit? If so, then that's a very good result for only 30% CPU.
>
> It means that the padlock is doing it's job in making crypto acceleration.
Without padlock I am seeing about 50% CPU use with 25 Mbit
Hello,
openssl with enabled padlock and tor stable crashes on my via nano
servers running linux and freebsd.
without padlock max is ~81 Mbit with linux and ~76 with freebsd (100%
load, measured in the last week).
On 05.06.2016 17:22, Roman Mamedov wrote:
> On Sun, 5 Jun 2016 17:01:29 +0200
> "F
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/05/2016 01:28 PM, Fabio Pietrosanti (naif) - lists wrote:
> In /etc/tor/torrc:
> HardwareAccel 1
Reading
https://lists.torproject.org/pipermail/tor-relays/2012-March/001260.html I do
wonder if setting that option is helpful ?
- --
Toralf
PG
Hi,
(Batching a bunch of replies together.)
For some historical context:
* https://trac.torproject.org/projects/tor/ticket/15503
* https://trac.torproject.org/projects/tor/ticket/15918 (Still
a low priority, padlock's hash accel isn't exposed in any way from
OpenSSL at all.)
On Sun, 5
On 6/5/16 9:40 PM, Yawning Angel wrote:
> The important one is AES-128-CTR. Since you're using OpenSSL master,
> it should be accelerated. Versions prior to the 1.1 series do not.
>
> Quickly skimming engines/e_padlock.c, it appears that GCM accel isn't
> supported, but I don't feel like looki
