2016-11-01 12:03 GMT-03:00, teor :
>
>> On 2 Nov. 2016, at 01:56, Felix wrote:
>> ...
>>
>> My log says:
>> Oct 19 01:04:52.527 [notice] Read configuration file
>> "/usr/local/etc/tor/torrc".
>> Oct 19 01:04:52.566 [notice] Opening OR listener on 0.0.0.0:1234
>> for
>> ORPort 443 NoListen
>> ORPor
> On 2 Nov. 2016, at 01:56, Felix wrote:
> ...
>
> My log says:
> Oct 19 01:04:52.527 [notice] Read configuration file
> "/usr/local/etc/tor/torrc".
> Oct 19 01:04:52.566 [notice] Opening OR listener on 0.0.0.0:1234
> for
> ORPort 443 NoListen
> ORPort 1234 NoAdvertise
> My Tor finds 0.0.0.0 an
Am 01.11.2016 um 13:19 schrieb Vinícius Zavam:
2016-10-31 20:22 GMT-03:00, Felix :
Am 31.10.2016 um 23:40 schrieb Vinícius Zavam:
2016-10-19 2:30 GMT-03:00, teor :
On 19 Oct. 2016, at 16:25, Felix wrote:
Hi everybody
May be someone can help with this warning:
The security update (Tor
2016-10-31 20:22 GMT-03:00, Felix :
>
>
> Am 31.10.2016 um 23:40 schrieb Vinícius Zavam:
>> 2016-10-19 2:30 GMT-03:00, teor :
>>>
On 19 Oct. 2016, at 16:25, Felix wrote:
Hi everybody
May be someone can help with this warning:
The security update (Tor v0.2.8.9 run
Am 31.10.2016 um 23:40 schrieb Vinícius Zavam:
2016-10-19 2:30 GMT-03:00, teor :
On 19 Oct. 2016, at 16:25, Felix wrote:
Hi everybody
May be someone can help with this warning:
The security update (Tor v0.2.8.9 running on FreeBSD with Libevent
2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zl
2016-10-19 2:30 GMT-03:00, teor :
>
>> On 19 Oct. 2016, at 16:25, Felix wrote:
>>
>> Hi everybody
>>
>> May be someone can help with this warning:
>>
>> The security update (Tor v0.2.8.9 running on FreeBSD with Libevent
>> 2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zlib 1.2.8.) shows the following
> On 19 Oct. 2016, at 16:46, Felix wrote:
>
> Thanks for picking up.
>
> > It would help us to know if it's just FreeBSD, or just LibreSSL.
> It's both LibreSSL on FreeBSD 10.1. Same setup worked fine since months
> through serveral versions of Tor (2.6.x and 2.7.x) and LibreSSL (2.2.x until
Thanks for picking up.
> It would help us to know if it's just FreeBSD, or just LibreSSL.
It's both LibreSSL on FreeBSD 10.1. Same setup worked fine since months
through serveral versions of Tor (2.6.x and 2.7.x) and LibreSSL (2.2.x
until today).
> Maybe mention the bug number on tor-talk, so
> On 19 Oct. 2016, at 16:25, Felix wrote:
>
> Hi everybody
>
> May be someone can help with this warning:
>
> The security update (Tor v0.2.8.9 running on FreeBSD with Libevent
> 2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zlib 1.2.8.) shows the following
> log entry each hour:
>
> Oct 19 02:
Hi everybody
May be someone can help with this warning:
The security update (Tor v0.2.8.9 running on FreeBSD with Libevent
2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zlib 1.2.8.) shows the
following log entry each hour:
Oct 19 02:51:07.000 [warn] Your system clock just jumped 136 seconds
for
10 matches
Mail list logo