On Thu, 12 Oct 2017 21:01:55 +0100 (BST)
Dylan Issa wrote:
> Maybe they're truncated, but they still need to start with a $
If you would just read the manual page, you would gather that $ is optional.
>
> On 12 October 2017 at 20:09 Sebastian Hahn wrote:
>
> Hi there,
>
> On 12. Oct 2017, at
Maybe they're truncated, but they still need to start with a $On 12 October 2017 at 20:09 Sebastian Hahn wrote:Hi there,On 12. Oct 2017, at 20:43, Scott Bennett wrote:teor wrote:On 12 Oct 2017, at 13:21, Toralf F?rster wrote:-BEGIN PGP SIGNED MESSAGE-Hash: SHA256On 10/11/2017 10:08 AM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/12/2017 08:43 PM, Scott Bennett wrote:
> Doessn't each fingerprint need to start with a $ character? Otherwise
> it's just a really long nickname, right?
That entry worked fine for eons and is realized fine, eg.:
https://atlas.torproject
Hi there,
> On 12. Oct 2017, at 20:43, Scott Bennett wrote:
> teor wrote:
>>> On 12 Oct 2017, at 13:21, Toralf F?rster wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>>
On 10/11/2017 10:08 AM, Dylan Issa wrote:
Did you set MyFamily using nicknames of the key?
>
teor wrote:
>
> > On 12 Oct 2017, at 13:21, Toralf F?rster wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> >> On 10/11/2017 10:08 AM, Dylan Issa wrote:
> >> Did you set MyFamily using nicknames of the key?
> >> Because if nickname, change it to key is basically what i
> On 12 Oct 2017, at 13:21, Toralf Förster wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>> On 10/11/2017 10:08 AM, Dylan Issa wrote:
>> Did you set MyFamily using nicknames of the key?
>> Because if nickname, change it to key is basically what it’s saying.
>
>
> No,
>
> bo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/11/2017 10:08 AM, Dylan Issa wrote:
> Did you set MyFamily using nicknames of the key?
> Because if nickname, change it to key is basically what it’s saying.
No,
both Tor processes share this common config file:
grep -i famil /etc/tor/torr
So far I have had no abuse emails or complaints after two months on a new
server, using the longer suggested reduced policy list, but I do exclude 80,
which seems safer but limits the role as an exit. But 443 open. I closed other
potential abuse ports such as 22, 8080, 5900.
It's not the compla
Hi Paul,
On 11/10/2017 13:28, Paul Templeton wrote:
>> I believe in such case you are supposed to reply to your provider
> I will
For my experience, I do the same.
>> There was a mini discussion recently on that, with the general consensus
>> seeming to be that keeping it open is more trouble th
On 12.10.2017 11:57, nusenu wrote:
>
> nusenu:
>> Jacki M:
>>> How do I revert back to a stable build of Tor from an alpha? Im running Tor
>>> 0.3.2.2-alpha and need to revert back to Tor 0.3.1.7.
>>> Im running Ubuntu 16.04.3 LTS.
>> this should be easy:
>>
>> apt remove tor
>> adjust sources.lis
nusenu:
> Jacki M:
>> How do I revert back to a stable build of Tor from an alpha? Im running Tor
>> 0.3.2.2-alpha and need to revert back to Tor 0.3.1.7.
>> Im running Ubuntu 16.04.3 LTS.
>
> this should be easy:
>
> apt remove tor
> adjust sources.list to point to the stable repository (remo
Jacki M:
> How do I revert back to a stable build of Tor from an alpha? Im running Tor
> 0.3.2.2-alpha and need to revert back to Tor 0.3.1.7.
> Im running Ubuntu 16.04.3 LTS.
this should be easy:
apt remove tor
adjust sources.list to point to the stable repository (remove the
experimental repo)
12 matches
Mail list logo