Gus,
It's "OnNoNotAnotherTorRelay";
D195E5CE8AE77BAC91673E6CFB7BD0AF57281646
Cheers.
On 9/9/2020 7:44 PM, gus wrote:
Hi Eddie,
Could you inform your relay fingerprint?
Thanks,
Gus
On Mon, Sep 07, 2020 at 11:54:47AM -0700, Eddie wrote:
Starting yesterday (maybe Saturday) we have been
Hi, question for Tor exit relay operators. Do exit relay operators allow
connections to SMTP port 587 more than port 465?
The RiseUp webpage says “SMTP port 465 is often blocked by Tor exit
nodes but port 587 is less frequently blocked”
(https://riseup.net/en/email/clients) because port 465 is
hi, generalized question about Tor exit relays and exit relay operators.
do some exit relay operators have a policy to prevent connections
leaving their exit node via non-encrypted ports (e.g. port 25)?
this could be a philosophical position - not even wanting to be in a
position to observe
On Thu, Sep 10, 2020 at 8:48 AM Dr Gerard Bulger
wrote:
> I know we should dilute our dependence on OVH, but cheap and seem to
> ignore the fact the machine is an exit node.
>
>
>
> OVH has a seemingly patented a system to deal with denial of service
> attacks. I am not sure what they detect
On Wed, Sep 09, 2020 at 12:00:37PM +0100, Dr Gerard Bulger wrote:
> To be fair, the automated system takes it off after an our or two. If my
> tor server is left in this mitigated state, the tor exit gets labelled a BAD
> EXIT which is something to avoid as takes days to be trusted again.
Can
I know we should dilute our dependence on OVH, but cheap and seem to ignore
the fact the machine is an exit node.
OVH has a seemingly patented a system to deal with denial of service
attacks. I am not sure what they detect but when they do we get this:
"We have just detected an attack on
