El 12/02/20 a las 07:02, ylms escribió:
>
>
> On 2/12/20 5:28 AM, skarz wrote:
> > 70 Mbps isn’t fast enough for Tor?
>
> I'd say it is not fast enough for Tor, we did some tests with a
> Raspberry Pi4 lately, these can utilize close to 100 MBit/s.
100Mbps used by Tor connections? Or what kind
El 04/09/18 a las 17:51, nusenu escribió:
…
> > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt
> > Authority X3
> > 34405378632:error:14090086:SSL
> > routines:ssl3_get_server_certificate:certificate verify
> > failed:/usr/src/crypto/openssl/ssl/s3_clnt.c:1269:
> >
El 04/09/18 a las 17:12, nusenu escribió:
>
>
> Paul:
> >
> > For me running several FreeBSD relays this is a great hint!
> >
> > Maybe it will find its way to
> > https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD
> >
>
> http replaced with https
>
El 11/05/18 a las 14:52, Ralph Seichter escribió:
> On 11.05.18 13:55, Nathaniel Suchy (Lunorian) wrote:
>
> > My first thought is to use ISP DNS if it’s available - one of the best
> > things about Tor is the split of trust so why aren’t we doing that
> > with DNS? Another alternative is to use
El 24/02/18 a las 19:54, Spiros Andreou escribió:
> Hi Olaf,
>
> SSH brute force attacks are commonplace on any internet facing server with
> port
> 22 open. You have a number of countermeasure options:
>
> 1) install fail2ban which will block anyone who fails a login 3 times
libpam-abl could
El 09/10/17 a las 09:32, Ralph Seichter escribió:
> On 08.10.2017 23:05, Santiago R.R. wrote:
>
> > I would also suggest to use DNS-over-TLS, so (exit) relays could be
> > able to encrypt their queries to a privacy-aware DNS resolver [...]
>
> I like SSL for the
El 08/10/17 a las 09:17, Ralph Seichter escribió:
> On 07.10.17 19:39, jpmvtd...@laposte.net wrote:
>
> > It looks like this package could introduce vulnerabilities if not
> > handled properly, because it provides more than just local DNS cache.
>
> Unless you have a particular reason to use
