<div dir="ltr"><font face="verdana, sans-serif" color="#0b5394">Would Tor relays work in a dynamic manner switching from one to another from time to time? I am at the beginning of my research regarding a Tor network and I could use some support from you, guys. I would read a bit about entry, middle and exit relays as well as layers of encryption, but I need more realistic explaination how all of these operate in a practice. Thank you!</font><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 10, 2016 at 11:01 PM, <span dir="ltr"><<a href="mailto:tor-relays-request@lists.torproject.org" target="_blank">tor-relays-request@lists.torproject.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send tor-relays mailing list submissions to<br>
<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:tor-relays-request@lists.torproject.org">tor-relays-request@lists.torproject.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:tor-relays-owner@lists.torproject.org">tor-relays-owner@lists.torproject.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of tor-relays digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Potwin, Kansas (Kenneth Freeman)<br>
2. First (positive) experiences with a Tor Relay on Raspberry<br>
Pi3 (fr33d0m4all)<br>
3. Re: First (positive) experiences with a Tor Relay on<br>
Raspberry Pi3 (Yawning Angel)<br>
4. First Relay (KAW)<br>
5. First Relay (KAW)<br>
6. Re: First Relay (pa011)<br>
7. Re: First (positive) experiences with a Tor Relay on<br>
Raspberry Pi3 (Tom Jorquera)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 10 Apr 2016 10:56:52 -0600<br>
From: Kenneth Freeman <<a href="mailto:kencf0618@riseup.net">kencf0618@riseup.net</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: [tor-relays] Potwin, Kansas<br>
Message-ID: <<a href="mailto:570A85D4.2060107@riseup.net">570A85D4.2060107@riseup.net</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
So this is why 114 Tor exit nodes are apparently operating from Potwin,<br>
Kansas! Figured it was a digital artifact. The article doesn't mention<br>
Tor itself, but the nominal fount really jumps out on TorFlow.<br>
<br>
<a href="http://fusion.net/story/287592/internet-mapping-glitch-kansas-farm/" rel="noreferrer" target="_blank">http://fusion.net/story/287592/internet-mapping-glitch-kansas-farm/</a><br>
<br>
<a href="https://torflow.uncharted.software/" rel="noreferrer" target="_blank">https://torflow.uncharted.software/</a><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 0xDD79757F.asc<br>
Type: application/pgp-keys<br>
Size: 3129 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/cf9f1a4a/attachment-0001.key" rel="noreferrer" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/cf9f1a4a/attachment-0001.key</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 836 bytes<br>
Desc: OpenPGP digital signature<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/cf9f1a4a/attachment-0001.sig" rel="noreferrer" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/cf9f1a4a/attachment-0001.sig</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 10 Apr 2016 17:52:20 +0000<br>
From: fr33d0m4all <<a href="mailto:fr33d0m4all@riseup.net">fr33d0m4all@riseup.net</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: [tor-relays] First (positive) experiences with a Tor Relay on<br>
Raspberry Pi3<br>
Message-ID: <<a href="mailto:570A92D4.5000006@riseup.net">570A92D4.5000006@riseup.net</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA512<br>
<br>
Hi,<br>
I've just moved my Tor relay installation from my alix1.c embedded<br>
system (500Mhz CPU with 256Mb ram) which was able to offer only 4Mbps<br>
(100% CPU utilization) to a new Raspberry Pi3 (quad-core 1.2Ghz 64-bit<br>
cpu with 1 GB ram). Some days ago I've seen some messages on the ML<br>
about Pi2 performance (if I remember well) and I'd like to share my<br>
first experiences with Pi3. I have only 20Mbps connection in the<br>
uplink direction, so I'm offering about 15Mbps for Tor relay and I've<br>
just seen that it is able to offer 14Mbps with 40% of a single core<br>
utilization.. In conclusion, I think that a single relay on Pi3 can<br>
offer about 30-40 Mbps, and if you run 4 tor relays on the same Pi3<br>
you can offer more than 100Mbps which is definitely not bad for such a<br>
small system. The only drawback is that you need to find a good way<br>
for keeping it cold, since after 1 hour of 1 core at 100% I've reached<br>
about 70?C with heatsinks on the CPU.<br>
<br>
I just wanted to share my experience with you, hope you find it<br>
interesting :)<br>
<br>
Have a nice week<br>
Fr33d0m4All<br>
<br>
- --<br>
<br>
_____________________________________________________________<br>
<br>
PGP Key: 0DA8 7293 D561 3AEE A3C0 7F63 101F 316A F30E ECB4<br>
IRC Nick: fr33d0m4all (OFTC & Freenode)<br>
_____________________________________________________________<br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iQIcBAEBCgAGBQJXCpLUAAoJEBAfMWrzDuy0KpQQAKG1Su24A3O1keFdPGk2zdzw<br>
lwEk+pSvRzfoHfmocv5ia9PQ8ZtBws3QfaxfZOYIA0DxdKVK7Rcs+r0ekL6VtAdp<br>
y3HU3SlAoCxFDsHycsPhuXZPmQqU/+OAS0lrzo2KrKk/lN/K+b2YYzLfJ+9SWzE1<br>
kg4dcCnWfQrMsLLK72R9qIjSmDsXDGzzNRq0qM3nDjDmE5GPmMJajSbWsHP12v/q<br>
BnA786RdB/CDiFVifGPYsKEuughpJ1ryVSRm3LdmTdIjZ+u/sxz0/TQrmj7idgdr<br>
TenFk4rf0NbiLU/7sruNJNYPFHvUMUOC8Xu7wBJU2LTF/8fcjYOaQp2UWch4aGQa<br>
nM4tMetvhEmoGxcEmJSsi2CHdLkMZ8G67gfufb7Gmsmd59q0KvRQktPxqnJ0GJIs<br>
20x2PX2qzXX7P4mKL8nO0aX32OP+1xScuSH/85Lu6Nnh1jL+T81QPjk/CUHB86ho<br>
gbuGt154KEnMoKx+w3aXrzSKVH5kRMgWhIcbRt/xELWprx2zsxGM+gIOCdLQ/vXi<br>
PugDblYL8sa8Uds6cz0fjNsuCBI19X0NlnmGFAbU9qOHEhUzYpuF4VlH7sOkL0n2<br>
HWkJTSIjizjZCS0PDPeaqj3lOtoFJiYcAxef+HnGEI/5dameIBB/MDJyOrf+oRfL<br>
1kNo6Zd5KqJesnljCac5<br>
=pk6h<br>
-----END PGP SIGNATURE-----<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 10 Apr 2016 18:28:30 +0000<br>
From: Yawning Angel <<a href="mailto:yawning@schwanenlied.me">yawning@schwanenlied.me</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] First (positive) experiences with a Tor<br>
Relay on Raspberry Pi3<br>
Message-ID: <<a href="mailto:20160410182830.2be8c166@schwanenlied.me">20160410182830.2be8c166@schwanenlied.me</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Sun, 10 Apr 2016 17:52:20 +0000<br>
fr33d0m4all <<a href="mailto:fr33d0m4all@riseup.net">fr33d0m4all@riseup.net</a>> wrote:<br>
> I've just moved my Tor relay installation from my alix1.c embedded<br>
> system (500Mhz CPU with 256Mb ram) which was able to offer only 4Mbps<br>
> (100% CPU utilization) to a new Raspberry Pi3 (quad-core 1.2Ghz 64-bit<br>
> cpu with 1 GB ram). Some days ago I've seen some messages on the ML<br>
> about Pi2 performance (if I remember well) and I'd like to share my<br>
> first experiences with Pi3. I have only 20Mbps connection in the<br>
> uplink direction, so I'm offering about 15Mbps for Tor relay and I've<br>
> just seen that it is able to offer 14Mbps with 40% of a single core<br>
> utilization.. In conclusion, I think that a single relay on Pi3 can<br>
> offer about 30-40 Mbps, and if you run 4 tor relays on the same Pi3<br>
> you can offer more than 100Mbps which is definitely not bad for such a<br>
> small system. The only drawback is that you need to find a good way<br>
> for keeping it cold, since after 1 hour of 1 core at 100% I've reached<br>
> about 70?C with heatsinks on the CPU.<br>
<br>
If you build tor against OpenSSL 1.1 on that target you will get a<br>
massive increase in performance due to support for the ARMv8 hardware<br>
AES acceleration.<br>
<br>
This requires 0.2.8.x from the maint-028 branch (or master if you're<br>
brave) since I recently fixed tor (again) to compile with this version<br>
of the library, but the changes will be in the next 0.2.8 release<br>
candidate.<br>
<br>
Regards,<br>
<br>
--<br>
Yawning Angel<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: OpenPGP digital signature<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/3ff32d8d/attachment-0001.sig" rel="noreferrer" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/3ff32d8d/attachment-0001.sig</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sun, 10 Apr 2016 15:09:07 -0400<br>
From: "KAW" <<a href="mailto:kawhunter@sigaint.org">kawhunter@sigaint.org</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: [tor-relays] First Relay<br>
Message-ID: <5390b0454b7f2274504046a39fa5f5d6.webmail@localhost><br>
Content-Type: text/plain;charset=iso-8859-1<br>
<br>
Got my first relay running for 4 days now :D<br>
<br>
<br>
-KAW<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sun, 10 Apr 2016 15:08:37 -0400<br>
From: "KAW" <<a href="mailto:kawhunter@sigaint.org">kawhunter@sigaint.org</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: [tor-relays] First Relay<br>
Message-ID: <b68a0e7f3801df57a5ea88fdaad3fd97.webmail@localhost><br>
Content-Type: text/plain;charset=iso-8859-1<br>
<br>
Got my first relay running for 4 days now :D<br>
<br>
<br>
-KAW<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Sun, 10 Apr 2016 22:14:37 +0200<br>
From: pa011 <<a href="mailto:pa011@web.de">pa011@web.de</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] First Relay<br>
Message-ID: <<a href="mailto:570AB42D.5010403@web.de">570AB42D.5010403@web.de</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Congratulation - I know that feeling very well ...one after another.... :-)<br>
<br>
Am 10.04.2016 um 21:08 schrieb KAW:<br>
> Got my first relay running for 4 days now :D<br>
><br>
><br>
> -KAW<br>
><br>
> _______________________________________________<br>
> tor-relays mailing list<br>
> <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
> <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 0xC8C330E7.asc<br>
Type: application/pgp-keys<br>
Size: 3104 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/01474be3/attachment-0001.key" rel="noreferrer" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/01474be3/attachment-0001.key</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Sun, 10 Apr 2016 23:01:21 +0200<br>
From: Tom Jorquera <<a href="mailto:tom@jorquera.net">tom@jorquera.net</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] First (positive) experiences with a Tor<br>
Relay on Raspberry Pi3<br>
Message-ID: <<a href="mailto:570ABF21.7090504@jorquera.net">570ABF21.7090504@jorquera.net</a>><br>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"<br>
<br>
On 10/04/2016 20:28, Yawning Angel wrote:<br>
> On Sun, 10 Apr 2016 17:52:20 +0000<br>
> fr33d0m4all <<a href="mailto:fr33d0m4all@riseup.net">fr33d0m4all@riseup.net</a>> wrote:<br>
>> I've just moved my Tor relay installation from my alix1.c embedded<br>
>> system (500Mhz CPU with 256Mb ram) which was able to offer only 4Mbps<br>
>> (100% CPU utilization) to a new Raspberry Pi3 (quad-core 1.2Ghz 64-bit<br>
>> cpu with 1 GB ram). Some days ago I've seen some messages on the ML<br>
>> about Pi2 performance (if I remember well) and I'd like to share my<br>
>> first experiences with Pi3. I have only 20Mbps connection in the<br>
>> uplink direction, so I'm offering about 15Mbps for Tor relay and I've<br>
>> just seen that it is able to offer 14Mbps with 40% of a single core<br>
>> utilization.. In conclusion, I think that a single relay on Pi3 can<br>
>> offer about 30-40 Mbps, and if you run 4 tor relays on the same Pi3<br>
>> you can offer more than 100Mbps which is definitely not bad for such a<br>
>> small system. The only drawback is that you need to find a good way<br>
>> for keeping it cold, since after 1 hour of 1 core at 100% I've reached<br>
>> about 70?C with heatsinks on the CPU.<br>
> If you build tor against OpenSSL 1.1 on that target you will get a<br>
> massive increase in performance due to support for the ARMv8 hardware<br>
> AES acceleration.<br>
><br>
> This requires 0.2.8.x from the maint-028 branch (or master if you're<br>
> brave) since I recently fixed tor (again) to compile with this version<br>
> of the library, but the changes will be in the next 0.2.8 release<br>
> candidate.<br>
><br>
> Regards,<br>
><br>
><br>
><br>
> _______________________________________________<br>
> tor-relays mailing list<br>
> <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
> <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
<br>
To follow up on your experience<br>
<br>
I am currently running a relay from a rasp3 with a bandwidth limit of 24<br>
Mb/s.<br>
<br>
I am using the tor package from raspbian (Tor 0.2.5.12).<br>
<br>
arm currently gives me the following informations:<br>
cpu: usually between 20.0% and 40%<br>
mem: 160 MB (17.3%)<br>
for a current average down and up of 35.3 Mb/sec and 36.1 Mb/sec (due to<br>
my high burst rating I suppose)<br>
<br>
The 15 mins load average of the raspy (which mostly runs tor) is 0.38.<br>
It may be biased by me running arm, which seems rather CPU intensive, to<br>
look things up for a while.<br>
<br>
I am not monitoring the temperature. The CPU seems a little hot to the<br>
touch, but not overly so. The rasp has an uptime of 14 days.<br>
<br>
All in all it seems to handle the load rather well!<br>
<br>
Regards,<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/532b3761/attachment.html" rel="noreferrer" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/532b3761/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
<br>
<br>
------------------------------<br>
<br>
End of tor-relays Digest, Vol 63, Issue 20<br>
******************************************<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><b style="font-size:12.8000001907349px;color:rgb(61,133,198)">A security is a process of maintaining an acceptable level of the risk.</b><b><br></b></div><div dir="ltr"><b><br></b></div><div dir="ltr"><b><font color="#073763">Milica Đekić</font></b></div><div dir="ltr"><div><b style="color:rgb(61,133,198);font-size:12.8000001907349px"><br></b></div><div><b style="font-size:12.8000001907349px"><font color="#3d85c6">Cybersecurity researcher</font></b><br></div><div><font color="#0b5394"><b style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">Twitter: @MilicaDjekic9</span></b><br></font></div><div><b><font color="#0b5394">Cell: +381 63 1963627</font></b></div><div><br></div><div><div><br></div><div><br></div><div><br></div><div><br></div></div></div></div></div></div></div></div></div></div></div></div>
</div></div>