Hi,
> On 7 Sep 2019, at 21:06,
> wrote:
>
> I have recently setup a new tor exit node but since about an hour of setting
> it up it has been almost maxed out with spam.
> https://metrics.torproject.org/rs.html#details/4AFECB973C2268D5074D8DEDAF0BDB604C89ED50
>
> How can I combat it?
>
> I
I have recently setup a new tor exit node but since about an hour of setting
it up it has been almost maxed out with spam.
https://metrics.torproject.org/rs.html#details/4AFECB973C2268D5074D8DEDAF0BD
B604C89ED50
How can I combat it?
I turned the node off for about an hour from about
> On Sep 7, 2019, at 04:13, s7r wrote:
>
> after upgrading from 0.4.1.2 to 0.4.2.0, I did an entire system
> reboot because I also updated some other stuff. So the entire OS
> restarted, not just Tor daemon
It seems likely that your machine's hardware clock is off. During a reboot, the
system
> On 7. Sep 2019, at 12:20, teor wrote:
>
> Hi,
>
> On 6 Sep 2019, at 20:14, Roman Mamedov wrote:
>
>>> Where does the security weakpoint risk come from? Does
>>> apt-transport-tor/onion service repository availability help in your
>>> mind here?
>>
>> As with adding any third-party
My relays track current stable, though I prefer going slow updating unless a
major CVE/TROVE lands.
LTS is beneficial for many reasons and, from the enthused developer perspective
perhaps best viewed as "necessary evil."
Rather than thinking about killing LTS, is better to think about ways to
On Sat, 7 Sep 2019 20:20:06 +1000
teor wrote:
> > As with adding any third-party repository, it means trusting the repository
> > provider to install and run any root-privilege code on the machine. In case
> > the repository server (or actually the release process, including signing)
> > is
> >
> Unfortunately, we still have something like 2500 relays on either Tor
> 0.2.9-LTS or Tor 0.3.5-LTS.
>
> What are the reasons for this? My guess is the top 5 most common
> responses are:
>
> 1. "I didn't know that Debian's backports repo has latest-stable Tor!"
> 2. "I didn't see the Tor
