<div>Unsub</div><div><br></div><div class="protonmail_signature_block"><div>Sent from <a href="https://protonmail.com">ProtonMail</a>, Swiss-based encrypted email.<br></div><div><br></div></div><blockquote class="protonmail_quote" type="cite"><div>-------- Original Message --------<br></div><div>Subject: tor-relays Digest, Vol 67, Issue 22<br></div><div>Local Time: August 8, 2016 2:00 AM<br></div><div>UTC Time: August 8, 2016 12:00 PM<br></div><div>From: tor-relays-request@lists.torproject.org<br></div><div>To: tor-relays@lists.torproject.org<br></div><div><br></div><div>Send tor-relays mailing list submissions to<br></div><div>
tor-relays@lists.torproject.org<br></div><div>
<br></div><div>
To subscribe or unsubscribe via the World Wide Web, visit<br></div><div>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br></div><div>
or, via email, send a message with subject or body 'help' to<br></div><div>
tor-relays-request@lists.torproject.org<br></div><div>
<br></div><div>
You can reach the person managing the list at<br></div><div>
tor-relays-owner@lists.torproject.org<br></div><div>
<br></div><div>
When replying, please edit your Subject line so it is more specific<br></div><div>
than "Re: Contents of tor-relays digest..."<br></div><div>
<br></div><div>
<br></div><div>
Today's Topics:<br></div><div>
<br></div><div>
1. Re: tor-relays Digest, Vol 67, Issue 12 (grarpamp)<br></div><div>
2. Re: is explicit DirPort needed anymore under Tor 0.2.8.6? (teor)<br></div><div>
3. Re: [PATCH] debian package upgrade restart issue (nusenu)<br></div><div>
<br></div><div>
<br></div><div>
----------------------------------------------------------------------<br></div><div>
<br></div><div>
Message: 1<br></div><div>
Date: Mon, 8 Aug 2016 01:40:59 -0400<br></div><div>
From: grarpamp <grarpamp@gmail.com><br></div><div>
To: tor-relays@lists.torproject.org<br></div><div>
Cc: flipchan@riseup.net<br></div><div>
Subject: Re: [tor-relays] tor-relays Digest, Vol 67, Issue 12<br></div><div>
Message-ID:<br></div><div>
<CAD2Ti2-2R0KE+KA6EkMwVftA8G8Bi9OV4sYr0k=a-5CD=WeFtg@mail.gmail.com><br></div><div>
Content-Type: text/plain; charset=UTF-8<br></div><div>
<br></div><div>
On 8/5/16, Flipchan <flipchan@riseup.net> wrote:<br></div><div>
> [bad netiquette]<br></div><div>
<br></div><div>
When replying to digests...<br></div><div>
- At minimum, change the subject to the original subject.<br></div><div>
Optimally also include proper header threading.<br></div><div>
Repliers should subscribe to per message distribution instead.<br></div><div>
- Delete all content from the original except some minimum<br></div><div>
needed to establish context to which you are replying,<br></div><div>
instead of spamming out longquotes of already said longtext.<br></div><div>
- Reply inline below each piece of context to which you are<br></div><div>
replying, instead of top posting.<br></div><div>
<br></div><div>
<br></div><div>
------------------------------<br></div><div>
<br></div><div>
Message: 2<br></div><div>
Date: Mon, 8 Aug 2016 17:33:42 +1000<br></div><div>
From: teor <teor2345@gmail.com><br></div><div>
To: tor-relays@lists.torproject.org<br></div><div>
Subject: Re: [tor-relays] is explicit DirPort needed anymore under Tor<br></div><div>
0.2.8.6?<br></div><div>
Message-ID: <6AABDA0A-4835-4B2C-A60D-A7A64568BE65@gmail.com><br></div><div>
Content-Type: text/plain; charset="utf-8"<br></div><div>
<br></div><div>
<br></div><div>
> On 3 Aug 2016, at 10:29, teor <teor2345@gmail.com> wrote:<br></div><div>
> <br></div><div>
> Clients on 0.2.7.6 and earlier still use the IPv4 DirPort.<br></div><div>
> (Tor Browser is still 0.2.7.6, and apps in general may take some time to upgrade.)<br></div><div>
> <br></div><div>
> Authorities on0.2.7.6 and earlier will only assign the HSDir flag to relays with an IPv4 DirPort.<br></div><div>
> (Authorities may take some time to upgrade, because running different versions increases authority diversity.)<br></div><div>
<br></div><div>
For the record, even though the man page entry for HidServDirectoryV2 says the DirPort is not required to be a HSDir, authorities on 0.2.7 and earlier still check for it before assigning the HSDir flag.<br></div><div>
<br></div><div>
Authorities on 0.2.8 and later behave in a way that's consistent with HidServDirectoryV2, assigning the HSDir flag to any relay that wants to be a HSDir, and either supports being a directory cache, or has a DirPort.<br></div><div>
<br></div><div>
HidServDirectoryV2 0|1<br></div><div>
When this option is set, Tor accepts and serves v2 hidden service<br></div><div>
descriptors. Setting DirPort is not required for this, because<br></div><div>
clients connect via the ORPort by default. (Default: 1)<br></div><div>
<br></div><div>
> Fallback directory mirrors must have a DirPort, and we'd only think about changing that when:<br></div><div>
> * all recommended relay versions are 0.2.8 and later, and<br></div><div>
> * relays no longer fetch documents using the DirPort (so maybe never).<br></div><div>
> <br></div><div>
> All relays running any Tor version will continue to use the IPv4 DirPort to fetch consensuses from other relays.<br></div><div>
> <br></div><div>
> So we haven't obsoleted the IPv4 DirPort yet. We've just made sure that clients fetch directory documents over an encrypted channel.<br></div><div>
<br></div><div>
Tim Wilson-Brown (teor)<br></div><div>
<br></div><div>
teor2345 at gmail dot com<br></div><div>
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B<br></div><div>
ricochet:ekmygaiu4rzgsk6n<br></div><div>
xmpp: teor at torproject dot org<br></div><div>
<br></div><div>
<br></div><div>
<br></div><div>
<br></div><div>
<br></div><div>
<br></div><div>
-------------- next part --------------<br></div><div>
A non-text attachment was scrubbed...<br></div><div>
Name: signature.asc<br></div><div>
Type: application/pgp-signature<br></div><div>
Size: 842 bytes<br></div><div>
Desc: Message signed with OpenPGP using GPGMail<br></div><div>
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160808/b29f3270/attachment-0001.sig><br></div><div>
<br></div><div>
------------------------------<br></div><div>
<br></div><div>
Message: 3<br></div><div>
Date: Mon, 08 Aug 2016 11:53:00 +0000<br></div><div>
From: nusenu <nusenu@openmailbox.org><br></div><div>
To: tor-relays@lists.torproject.org<br></div><div>
Subject: Re: [tor-relays] [PATCH] debian package upgrade restart issue<br></div><div>
Message-ID: <14e8de2a-577d-6498-e976-0002545b5a7e@openmailbox.org><br></div><div>
Content-Type: text/plain; charset="utf-8"<br></div><div>
<br></div><div>
>> When upgrading, all running tor instances are stopped (not restarted, as expected)<br></div><div>
> <br></div><div>
> This might be your root-cause as well?<br></div><div>
> <br></div><div>
> https://github.com/nusenu/ansible-relayor/issues/72<br></div><div>
> <br></div><div>
> I'm generating instance names based on IP addresses_ORport (so they<br></div><div>
> contain "." and "_") and are therefore filtered by the generator.<br></div><div>
> <br></div><div>
> Is it acceptable to add "." and "_" to the whitelist?<br></div><div>
> <br></div><div>
> (patches attached)<br></div><div>
<br></div><div>
Based on the output of 'systemd-escape' (a tool that escapes strings for<br></div><div>
use in unit names) it is safe to use "." and "_" in unit names.<br></div><div>
<br></div><div>
-------------- next part --------------<br></div><div>
A non-text attachment was scrubbed...<br></div><div>
Name: signature.asc<br></div><div>
Type: application/pgp-signature<br></div><div>
Size: 801 bytes<br></div><div>
Desc: OpenPGP digital signature<br></div><div>
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160808/73daa746/attachment-0001.sig><br></div><div>
<br></div><div>
------------------------------<br></div><div>
<br></div><div>
Subject: Digest Footer<br></div><div>
<br></div><div>
_______________________________________________<br></div><div>
tor-relays mailing list<br></div><div>
tor-relays@lists.torproject.org<br></div><div>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br></div><div>
<br></div><div>
<br></div><div>
------------------------------<br></div><div>
<br></div><div>
End of tor-relays Digest, Vol 67, Issue 22<br></div><div>
******************************************<br></div></blockquote>