One suggestion I’ll add is
https://tornull.org has a huge exit policy with common sinkholes and other
abusive networks. You won’t stop them all BUT it may reduce the complaints
your ISP gets.
Cordially,
Nathaniel
On Fri, Sep 7, 2018 at 12:51 PM nusenu wrote:
> before tackling the actual questio
before tackling the actual question, a short description of how detection of
malware activity is
usually performed in this context - at least in the context of these kinds of
"abuse" emails:
* organizations like shadowservers [1] and others operate sinkhole servers that
listen
for incoming conn
On 07-09-18 15:17, Nathaniel Suchy wrote:
This is something you need to talk to your ISP about. Communicate with
them and see if they can work something out.
The ISP whitelisted my IP in their quarantine system to avoid this issue
next time.
This solves only the local part of the issue, thoug
This is something you need to talk to your ISP about. Communicate with them
and see if they can work something out.
Cordially,
Nathaniel
On Fri, Sep 7, 2018 at 9:14 AM Udo van den Heuvel wrote:
> On 07-09-18 15:10, Nathaniel Suchy wrote:
> > Talk to your ISP about what Tor is and ask them to di
On 07-09-18 15:10, Nathaniel Suchy wrote:
Talk to your ISP about what Tor is and ask them to disable the virus filter
on your account.
Thanks..
But local ISP is only one side.
The virus stuff goes somewhere and will also be detected elsewhere.
Then mail will be blacklisted (because a virus does
Port numbers might “limit” traffic when a service is using default ports.
However I could configure SSH to run on port 80 without an issue.
Similarly, no matter what the port is, a malware author can use it to send
malware out.
Talk to your ISP about what Tor is and ask them to disable the virus
Hello,
In the past I opened up some 'innocent' exit ports and after a while my
ISP detected a Windows virus of some sorts from my IP('s).
So I went to relay only and that problem was fixed.
Then I thought I was `smart` and opened just a few ports that (normally)
carry SSL-protected connection