<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div></div>
<div>Daniel,</div>
<div><br>
</div>
<div>No. Part of being a Tor Relay is sticking your neck out a bit for those who can't. No one will fault you if you decide to not run a relay.</div>
<div><br>
</div>
<div>John</div>
<div><br>
On Sep 6, 2016, at 23:08, daniel boone <<a href="mailto:homer2@gmx.com">homer2@gmx.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Relay Issue: I had a relay up and runnng Saturday. I found my relay Atlas but I did not like what I saw on there. It showed my isp number and my dsl provider so I shut down the relay. Is there some adjustment in the "torrc" file to have that not show.
And I do not have any access to a Proxy Sever.</div>
<div>tks</div>
<div>-DB-</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Sent:</b> Tuesday, September 06, 2016 at 6:39 PM<br>
<b>From:</b> <a href="mailto:tor-relays-request@lists.torproject.org">tor-relays-request@lists.torproject.org</a><br>
<b>To:</b> <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
<b>Subject:</b> tor-relays Digest, Vol 68, Issue 21</div>
<div name="quoted-content">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" 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. write-history for exit relays only? (Philipp Winter)<br>
2. Re: write-history for exit relays only? (Aaron Johnson)<br>
3. Re: Tor and Diplomatic Immunity (Green Dream)<br>
4. Re: Tor and Diplomatic Immunity (ITechGeek)<br>
5. Which OS gives usually the best performance for a relay?<br>
(Farid Joubbi)<br>
6. Re: write-history for exit relays only? (Philipp Winter)<br>
7. Re: write-history for exit relays only? (teor)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 6 Sep 2016 11:06:57 -0400<br>
From: Philipp Winter <<a href="mailto:phw@nymity.ch">phw@nymity.ch</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: [tor-relays] write-history for exit relays only?<br>
Message-ID: <<a href="mailto:20160906150657.GA2619@riseup.net">20160906150657.GA2619@riseup.net</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
I want to learn how many bytes exit relays forwarded. I assume that the<br>
write-history that is published in a relay's extra-info document<br>
includes bytes that were relayed as part of the exit's guard and middle<br>
role? If so, is there a way to learn how many bytes were written by the<br>
relay in its exit role only?<br>
<br>
I suspect that one could approximate this number by accounting for the<br>
probability of all exits being selected as guard, middle, and exit, but<br>
I would prefer a simpler and more reliable approach.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 6 Sep 2016 12:10:06 -0400<br>
From: Aaron Johnson <<a href="mailto:aaron.m.johnson@nrl.navy.mil">aaron.m.johnson@nrl.navy.mil</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] write-history for exit relays only?<br>
Message-ID: <<a href="mailto:6FEEF628-5016-4F5A-B0DC-087053CBD1C7@nrl.navy.mil">6FEEF628-5016-4F5A-B0DC-087053CBD1C7@nrl.navy.mil</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
> I suspect that one could approximate this number by accounting for the<br>
> probability of all exits being selected as guard, middle, and exit, but<br>
> I would prefer a simpler and more reliable approach.<br>
<br>
This doesn’t seem like a bad approximation to me, given that for as long as I have been aware, exits have had zero probability of being chosen in any position other than the exit position.<br>
<br>
Aaron<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 6 Sep 2016 11:29:27 -0700<br>
From: Green Dream <<a href="mailto:greendream848@gmail.com">greendream848@gmail.com</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] Tor and Diplomatic Immunity<br>
Message-ID:<br>
<<a href="mailto:CAAd2PD+755jb-hU++H8BTuWDkkNMKbDy2LFmaZLXontT5DgpOw@mail.gmail.com">CAAd2PD+755jb-hU++H8BTuWDkkNMKbDy2LFmaZLXontT5DgpOw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
The whole idea doesn't sit right with me.<br>
<br>
For one, I'm not sure I'd want any more Five Eyes entities running<br>
Exit nodes. Most embassies are already a haven for espionage activity.<br>
You'd pretty much have to assume they'd be sniffing the exit traffic.<br>
<br>
Also, with all the other priorities, I kinda doubt most embassies have<br>
any interest in the general work involved, not to mention the<br>
liability, of running an Exit.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 6 Sep 2016 14:49:56 -0400<br>
From: ITechGeek <<a href="mailto:ITG@itechgeek.com">ITG@itechgeek.com</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] Tor and Diplomatic Immunity<br>
Message-ID:<br>
<<a href="mailto:CAN2EnhD7E=DYynJDGr+Pu-Vx7wMQGN6FV5KdgksGT8VK42HOxA@mail.gmail.com">CAN2EnhD7E=DYynJDGr+Pu-Vx7wMQGN6FV5KdgksGT8VK42HOxA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Tue, Sep 6, 2016 at 2:29 PM, Green Dream <<a href="mailto:greendream848@gmail.com">greendream848@gmail.com</a>> wrote:<br>
<br>
> For one, I'm not sure I'd want any more Five Eyes entities running<br>
> Exit nodes. Most embassies are already a haven for espionage activity.<br>
> You'd pretty much have to assume they'd be sniffing the exit traffic.<br>
><br>
<br>
I doubt Five Eyes countries embassies would bother running tor since they<br>
have budgets to easily encrypt and funnel all their traffic back to their<br>
home countries.<br>
<br>
If anyone would be running tor nodes, I would imagine it would be countries<br>
w/ smaller budgets who would be looking for more cost effective ways to<br>
make their traffic hard to sniff.<br>
<br>
<br>
-----------------------------------------------------------------------------------------------<br>
-ITG (ITechGeek) | <a href="mailto:ITG@itechgeek.com">ITG@ITechGeek.Com</a> <<a href="https://itg.nu/" target="_blank">https://itg.nu/</a>><br>
<a href="https://keybase.io/itechgeek" target="_blank">https://keybase.io/itechgeek</a> |
<a href="https://itg.nu/" target="_blank">https://itg.nu/</a><br>
Google Voice: +1-703-493-0128 / Twitter: ITechGeek / Facebook:<br>
<a href="http://fb.me/Jbwa.Net" target="_blank">http://fb.me/Jbwa.Net</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160906/9c226ed9/attachment-0001.html" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160906/9c226ed9/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 6 Sep 2016 20:14:38 +0000<br>
From: Farid Joubbi <<a href="mailto:joubbi@kth.se">joubbi@kth.se</a>><br>
To: "<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a>"<br>
<<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a>><br>
Subject: [tor-relays] Which OS gives usually the best performance for<br>
a relay?<br>
Message-ID: <<a href="mailto:1473192878111.13336@kth.se">1473192878111.13336@kth.se</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hello,<br>
<br>
<br>
I am thinking of setting up a new relay.<br>
<br>
I know that the hardware in the server is going to be the bottleneck, not my Internet connection.<br>
<br>
I have a problem deciding on which OS to use for the relay.<br>
<br>
A few years ago when I had a similar relay going, I had it running on OpenBSD first.<br>
<br>
Then I changed the OS to FreeBSD and the performance got about 20% better.<br>
<br>
I have no idea if this would be the case today too.<br>
<br>
So I think that maybe it's either FreeBSD or Debian that would be "best", but I have nothing concrete to base that decision on unless I try them both.<br>
<br>
<br>
I am going to use a Via C7 board in this specific case. So I suspect that it's the maturity of the VIA drivers in the OS that is going to make the difference. Still I would like to know how to think in similar situations in the future even for other hardware.<br>
<br>
<br>
Has anyone any concrete experience of the tor relay speeds on different operating systems?<br>
<br>
I don't want to start a flame war of religious beliefs, but I suspect that OSes differ in how optimized they are for different tasks.<br>
<br>
<br>
Thankful for any constructive input on this.<br>
<br>
<br>
Regards,<br>
<br>
Farid<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160906/311d8e64/attachment-0001.html" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160906/311d8e64/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 6 Sep 2016 16:36:23 -0400<br>
From: Philipp Winter <<a href="mailto:phw@nymity.ch">phw@nymity.ch</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] write-history for exit relays only?<br>
Message-ID: <<a href="mailto:20160906203623.GB2619@riseup.net">20160906203623.GB2619@riseup.net</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Tue, Sep 06, 2016 at 12:10:06PM -0400, Aaron Johnson wrote:<br>
> > I suspect that one could approximate this number by accounting for the<br>
> > probability of all exits being selected as guard, middle, and exit, but<br>
> > I would prefer a simpler and more reliable approach.<br>
><br>
> This doesn’t seem like a bad approximation to me, given that for as<br>
> long as I have been aware, exits have had zero probability of being<br>
> chosen in any position other than the exit position.<br>
<br>
Thanks, Aaron. You are right. Section 3.8.3 in dir-spec has the answer:<br>
<<a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2611" target="_blank">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2611</a>><br>
<br>
I just proved this to myself with the small attached Python script.<br>
Currently, exit bandwidth is the network's scarce resource, which is not<br>
surprising since running an exit is riskier than running a guard or a<br>
middle. Since exits are scarce, the bandwidth weights in case 3,<br>
subcase A are currently in place:<br>
<<a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2726" target="_blank">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2726</a>><br>
<br>
In that case, the specification hard-codes the probability of an exit<br>
taking on a non-exit role (Wgd, Wmd, and Wme) to 0.<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: bandwidth-weights.py<br>
Type: text/x-python<br>
Size: 1318 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160906/cf321b8e/attachment-0001.py" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160906/cf321b8e/attachment-0001.py</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 7 Sep 2016 08:39:24 +1000<br>
From: teor <<a href="mailto:teor2345@gmail.com">teor2345@gmail.com</a>><br>
To: <a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
Subject: Re: [tor-relays] write-history for exit relays only?<br>
Message-ID: <<a href="mailto:A6898E13-C01F-441A-B392-2912376AB7D4@gmail.com">A6898E13-C01F-441A-B392-2912376AB7D4@gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
> On 7 Sep 2016, at 06:36, Philipp Winter <<a href="mailto:phw@nymity.ch">phw@nymity.ch</a>> wrote:<br>
><br>
> On Tue, Sep 06, 2016 at 12:10:06PM -0400, Aaron Johnson wrote:<br>
>>> I suspect that one could approximate this number by accounting for the<br>
>>> probability of all exits being selected as guard, middle, and exit, but<br>
>>> I would prefer a simpler and more reliable approach.<br>
>><br>
>> This doesn’t seem like a bad approximation to me, given that for as<br>
>> long as I have been aware, exits have had zero probability of being<br>
>> chosen in any position other than the exit position.<br>
><br>
> Thanks, Aaron. You are right. Section 3.8.3 in dir-spec has the answer:<br>
> <<a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2611" target="_blank">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2611</a>><br>
><br>
> I just proved this to myself with the small attached Python script.<br>
> Currently, exit bandwidth is the network's scarce resource, which is not<br>
> surprising since running an exit is riskier than running a guard or a<br>
> middle. Since exits are scarce, the bandwidth weights in case 3,<br>
> subcase A are currently in place:<br>
> <<a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2726" target="_blank">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2726</a>><br>
><br>
> In that case, the specification hard-codes the probability of an exit<br>
> taking on a non-exit role (Wgd, Wmd, and Wme) to 0.<br>
> <bandwidth-weights.py><br>
<br>
It's also worth noting that Exits will serve directory documents and hidden service descriptors, and act as introduction and rendezvous points, so your estimates could be a few percentage points off.<br>
<br>
Tim<br>
<br>
Tim Wilson-Brown (teor)<br>
<br>
teor2345 at gmail dot com<br>
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B<br>
ricochet:ekmygaiu4rzgsk6n<br>
xmpp: teor at torproject dot org<br>
<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 842 bytes<br>
Desc: Message signed with OpenPGP using GPGMail<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20160907/9852a20a/attachment.sig" target="_blank">http://lists.torproject.org/pipermail/tor-relays/attachments/20160907/9852a20a/attachment.sig</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" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
<br>
<br>
------------------------------<br>
<br>
End of tor-relays Digest, Vol 68, Issue 21<br>
******************************************</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>tor-relays mailing list</span><br>
<span><a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a></span><br>
<span><a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a></span><br>
</div>
</blockquote>
</body>
</html>