> On 3 Aug 2016, at 10:29, teor wrote:
>
> Clients on 0.2.7.6 and earlier still use the IPv4 DirPort.
> (Tor Browser is still 0.2.7.6, and apps in general may take some time to
> upgrade.)
>
> Authorities on0.2.7.6 and earlier will only assign the HSDir flag to relays
> with an IPv4 DirPort.
>> When upgrading, all running tor instances are stopped (not restarted, as
>> expected)
>
> This might be your root-cause as well?
>
> https://github.com/nusenu/ansible-relayor/issues/72
>
> I'm generating instance names based on IP addresses_ORport (so they
> contain "." and "_") and are ther
On Mon, 08 Aug 2016, nusenu wrote:
> >> When upgrading, all running tor instances are stopped (not restarted, as
> >> expected)
> >
> > This might be your root-cause as well?
> >
> > https://github.com/nusenu/ansible-relayor/issues/72
> >
> > I'm generating instance names based on IP addresses
>>> I'm generating instance names based on IP addresses_ORport (so they
>>> contain "." and "_") and are therefore filtered by the generator.
>>>
>>> Is it acceptable to add "." and "_" to the whitelist?
>>>
>>> (patches attached)
>>
>> Based on the output of 'systemd-escape' (a tool that escapes s
A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with Ope
