niftybunny:
> Just woke up. So, whats wrong with some of my relays in this list?
some "exit" relay routed its traffic back into tor by using
a tor client. That tor client used exit relays - yours were among them.
So nothing wrong on your side.
signature.asc
Description: OpenPGP digital
My ISP (Hurricane Electric) forwards me support tickets with abuse emails
they receive, and asks that I respond to their ticket with information so
they can show that they did their duty as an ISP in informing me.
Because I typically get floods of this abuse-SPAM from only a few dedicated
>The provider said it was due to Spectre mitigations and the only way for me
to fix this would be to switch to a newer (more expensive) plan...
What?
Your provider lied to you / scammed you, Spectre/Meltdown etc.
mitigations have nothing to do with applications freezing or having to
get a faster
Torrc allows you to exit from a different IP. I thought it a good idea to stop
arbitrary blocking of the advertised Tor exit IP, the captchas and blacklists
that tor users suffer. When IPv6 implemented fully we have a wide range of IPs
to send from on each server.
Perhaps it is not
> On 9/28/20 1:54 PM, Matt Corallo wrote:
>
>> Different folks have different views on abuse reports, and that's
>> perfectly OK. But "taking it up with list XYZ" isn't
>> going to change that (see discussion on NANOG a few months ago on this
>> very topic =D) - people are always going to have
Just woke up. So, whats wrong with some of my relays in this list?
nifty
> On 12. Oct 2020, at 00:13, li...@for-privacy.net wrote:
>
> On 11.10.2020 22:41, Roger Dingledine wrote:
>
>> Right, in this particular case, we already run a scanner which provides
>> public output: it's the tordnsel
Hi all,
some weeks ago, my relay JPsi2
(F6EC46933CE8D4FAD5CCDAA8B1C5A377685FC521) started experiencing moderate
stability problems. It would freeze after a few hours or days. The
provider said it was due to Spectre mitigations and the only way for me
to fix this would be to switch to a newer
