News for hackers. Stuff that matters.
Re:You don’t want to be on Cloudflare’s naughty list by shaky-carrousel on Tuesday September 20, 2022 @03:21PM (#32916546)
I live in a country with censored internet. What you are doing is harmful. I can only hope whatever you provide is irrelevant enough.
Re:You don’t want to be on Cloudflare’s naughty list by thaumaturgy on Tuesday September 20, 2022 @03:42PM (#32916786)
I'm sorry. I have a colleague based out of Venezuela. We've had to work together to get tunnels and vpns configured so that he can get uncensored and secure internet access.

But Tor is an enormous source of abusive traffic and if I don't filter it, then that's harmful to site owners. I'm being forced to choose between the needs of people that I know, work with, and depend on financially, and the needs of people in countries with issues that are far outside my ability to resolve. It's not a hard decision.

Re:You don’t want to be on Cloudflare’s naughty list by Zak on Tuesday September 20, 2022 @04:59PM (#32917719)
There are probably more sophisticated options that would solve your problems than simply blocking it.
Re:You don’t want to be on Cloudflare’s naughty list by plumeria on Tuesday September 20, 2022 @05:57PM (#32918340)
Is using CAPTCHAs one of those?
Re:You don’t want to be on Cloudflare’s naughty list by throwaway0x7E6 on Wednesday September 21, 2022 @01:19AM (#32921067)
captchas are fine. recaptcha is not.

between 2015 and ~2020, my home ISP was blessed with every recaptcha being 3 rounds of slow fade-in bullshit. I have also seen infuriating gaslighting of "please try again" after certainly correct solutions, as well as 5+ rounds followed by a notification that my network is entirely blocked.

I've developed a reflex to Ctrl+W upon seeing it, unless that is absolutely vital for me to get past it - which is exceedingly rare.

if I had a genie lamp, I'd waste one of my 3 wishes to do terrible things to the people responsible for that shit.

Re:You don’t want to be on Cloudflare’s naughty list by Schroedingersat on Tuesday September 20, 2022 @11:45PM (#32920630)
Most captcha services are just used to force users identified as having few other options into giving free tagging labour.
Re:You don’t want to be on Cloudflare’s naughty list by judge2020 on Tuesday September 20, 2022 @05:48PM (#32918251)
Such as?
Re:You don’t want to be on Cloudflare’s naughty list by cowtools on Tuesday September 20, 2022 @06:09PM (#32918472)
The answer depends on the type of service you host. I don't know what you need to do, but I do know that filtering IP space is merely security-by-obscurity, it is a cheap and broken solution to the hard problems of sybil resistance. If you need IP filtering to operate on a day-to-day basis, then the security of your service is fundamentally broken.

Tor users do not have any special properties over clear-net users besides low accountability for their IP space. There are other ways to acquire this type of setup that don't involve broadcasting a public list of known exit nodes as an act of good faith. Any sophisticated attacker will be able to easily get ahold of the IP space and bandwidth they need to do their work, whether it's through a botnet or simply because they operate out of some less-accountable country like China or Russia.

IP filtering: now you have two problems!

Re:You don’t want to be on Cloudflare’s naughty list by thaumaturgy on Tuesday September 20, 2022 @06:17PM (#32918541)
This is why I'm strongly against spam filtering for email. Spam filters are fundamentally security-through-obscurity. I mean, they don't protect your email from targeted bombing attacks or phishing. If you need spam filters to operate your email on a day-to-day basis, then the security of your email is fundamentally broken.

/s, obviously, I hope.

Blocking Tor isn't a security measure, it's a nuisance reduction measure.

Re:You don’t want to be on Cloudflare’s naughty list by cowtools on Wednesday September 21, 2022 @12:39AM (#32920855)
>This is why I'm strongly against spam filtering for email. Spam filters are fundamentally security-through-obscurity. I mean, they don't protect your email from targeted bombing attacks or phishing. If you need spam filters to operate your email on a day-to-day basis, then the security of your email is fundamentally broken.

You kid, but this is completely true Email is simply an incredibly flawed, outdated and broken system, especially when used without PGP. Phishing is a massive problem, and it has only continued to grow in scale because spam, uh... finds a way. At the same time, spam filters regularly create false positives, making email an unreliable transport (leading "oops, it got lost in my spam folder").

>Blocking Tor isn't a security measure, it's a nuisance reduction measure.

You should block all IP space, this will reduce nuisances by 100%. In fact, this will save you from having to consider any real security practices or do your job properly.

Re:You don’t want to be on Cloudflare’s naughty list by matjet on Wednesday September 21, 2022 @12:58AM (#32920951)
The correct analogy here would be implementing spam filtering by blocking large segments of email addresses. Eg, dropping mail from all non microsoft/gmail domains (as a nuisance reduction measure!), with predictable impact on smaller providers and self hosted email.
Re:You don’t want to be on Cloudflare’s naughty list by thaumaturgy on Wednesday September 21, 2022 @02:03AM (#32921290)
You're reframing this to make Tor look a lot better than it is. The signal:noise ratio for Tor is epsilon. It's almost entirely garbage. If a network generated spam at rates analogous to network traffic from Tor, yes, I guarantee that network would be on every single email service's block list.

Tor's advocates in this thread keep trying to argue it from ideology, as though anybody's obligated to deal with Tor traffic on principle alone, and not one of them so far has tried to argue that Tor is not 90+% bots and garbage. Funny, that.

Re:You don’t want to be on Cloudflare’s naughty list by swores on Wednesday September 21, 2022 @03:12AM (#32921715)
With all the blocks in place, is it ever possible to know whether the 90% is still an innate effect of Tor, or actually an effect of sites blocking Tor?

I have Tor installed, figured it would be worth adding my boring browsing to the mix sometimes, but since most sites I try to load block Tor exits, Tor browser now sits unused.

On the other hand, if I woke up tomorrow deciding to start a bot farm or whatever other malicious thing, or course I'd be interested in hiding through Tor and might try it again (don't worry, I won't wake up that way).

So even if a hypothetical 100% of global internet users really wanted to do all their browsing through Tor, they might all reach the same conclusion as me that too many sites are blocked and therefore leave Tor to mostly bad traffic. Of course it's nowhere near 100%, but hopefully you see my point that the sites blocking Tor IPs (and I absolutely appreciate why) can become a self-fulfilling prophecy - and I'm not sure how you'd get out of that loop?

Re:You don’t want to be on Cloudflare’s naughty list by account42 on Wednesday September 21, 2022 @09:52AM (#32925171)
And if everyone blocks all non-gmail addresses then soon enough the snr of non-gmail addresses will also be garbage because you are actively preventing any legitimate user from using them.
Re:You don’t want to be on Cloudflare’s naughty list by plumeria on Wednesday September 21, 2022 @01:44AM (#32921210)
I think it would be sensible to block new account registrations with addresses from email address aliasing services (e.g. duck.com) or disposable email address services (e.g. mailinator.com).
Re:You don’t want to be on Cloudflare’s naughty list by account42 on Wednesday September 21, 2022 @09:49AM (#32925125)
I am strongly against any kind of spam filtering that drops/rejects messages that the recipient did not intentionally configure for those kinds of messages. Sorting suspicious mail into a separate folder is fine, preventing two humans from communicaing based on heuristics, IP block reputation and other such bs is not.
Re:You don’t want to be on Cloudflare’s naughty list by twno1 on Sunday October 02, 2022 @09:50AM (#33055848)
Outlook did that actually (preventing two humans from communication without reason)

https://www.linode.com/community/questions/22305/entire-ip-r...

Re:You don’t want to be on Cloudflare’s naughty list by justsomehnguy on Tuesday September 20, 2022 @04:05PM (#32917076)
> It's not a hard decision.

Depends on what you imply under 'hard'.

As a IaaS provider I endured alk the hurdles about that and ten years later - I don't care, at least not until my outbound bill is bigger than usual.

Like some of the clients are on CentOS6, on a public facing machines.

Re:You don’t want to be on Cloudflare’s naughty list by parroteal on Tuesday September 20, 2022 @05:18PM (#32917929)
I'm a noob, can you give me a pointer?

What kind of abusive traffic is coming through Tor and why do they do it?

Re:You don’t want to be on Cloudflare’s naughty list by thaumaturgy on Tuesday September 20, 2022 @06:03PM (#32918419)
Mainly forms -- login forms, comment forms, signup forms. Bots use Tor pretty heavily because it's anonymous and hard to block them without blocking the entire network. Login form abuse is mildly irritating but not a huge deal if you have other measures in place. Comment spam is annoying but there are some options that deal with it pretty well.

But the signup spam was a headache. I didn't want to just blackhole Tor traffic, and tried to reduce the abuse with other tools, including some custom stuff. The final straw was a customer's small business site that had a MailChimp or Constant Contact signup form. Those vendors want you to embed their code by default to render the form, so you have less control over the form itself. There were workarounds, but they all sucked.

Tor bots would sign up email addresses through this newsletter form, and then I'd have to go through and manually scrub them before newsletters went out, or the service would penalize my client for too many bounces/unsubscribes/complaints. Very nearly 100% of the abuse on that particular form came from Tor IPs.

I do not want to spend my limited time on this Earth manually sorting out bots from humans because of one particular network. Blackholing Tor made that problem disappear immediately.

VPNs are dime-a-dozen now, cheap VPSs are available from lots of vendors, there's Wireguard, there's ssh, a clever person could even set up Apache or nginx as a forward proxy with ssl from LetsEncrypt. Tor is well over 90% abusive traffic (https://blog.cloudflare.com/the-trouble-with-tor/). This is a Tor problem, not a me problem. There are better alternatives available.

Re:You don’t want to be on Cloudflare’s naughty list by mjevans on Tuesday September 20, 2022 @07:56PM (#32919349)
I think the workflow is the issue with http(s)-based email list sign-ups.

Solution: Require sign-ups by email, so the end account must actively send your mailserver a registration message. This also turns an open-loop control system into a closed loop control system, which is inherently easier to secure / keep safe.

Re:You don’t want to be on Cloudflare’s naughty list by gregmac on Wednesday September 21, 2022 @01:05AM (#32920993)
How would this be better? It's trivially easy to spoof email addresses. Someone could sign you up easily, for example.

It's also easy to send "from" an addresses that passes SPIF/DKIM but bounces inbound mail -- not sure what reason someone would have for this other than hurting the service reputation or acting as a DoS of sorts, but it can be done.

Re:You don’t want to be on Cloudflare’s naughty list by 3np on Wednesday September 21, 2022 @01:22AM (#32921087)
> It's trivially easy to spoof email addresses. Someone could sign you up easily, for example.

Proper DMARC configuration is table stakes to send e-mail, which makes that anything but trivial.

Re:You don’t want to be on Cloudflare’s naughty list by viraptor on Wednesday September 21, 2022 @07:40AM (#32923620)
But neither the newsletter host nor the email user has any input into how dmarc/dkim/spf are implemented. Only the user's email provider does. And if that's a small business domain, it's likely not very strict with the rules.
Re:You don’t want to be on Cloudflare’s naughty list by namibj on Wednesday September 21, 2022 @11:12AM (#32926275)
I thought DMARC/DKIM was necessary for delivering to Gmail for years now; in any case, there should be few who can't use a backup email to subscribe, as your newsletter won't be the only thing that has these anti-spoof requirements.
Re:You don’t want to be on Cloudflare’s naughty list by viraptor on Thursday September 22, 2022 @12:57AM (#32934942)
Not necessary. Just very highly recommended. I can still deliver my cron emails from a rando host successfully.
Re:You don’t want to be on Cloudflare’s naughty list by namibj on Sunday September 25, 2022 @10:12AM (#32971512)
That doesn't rule out DKIM, which only requires the `From:` header's domain to list a pubkey and the email to include a DKIM signature from a matching private key. SPF is the one that regulates which hosts a domain's outbound SMTP servers are on.
Re:You don’t want to be on Cloudflare’s naughty list by Schroedingersat on Tuesday September 20, 2022 @11:47PM (#32920642)
> Mainly forms -- login forms, comment forms, signup forms. Bots use Tor pretty heavily because it's anonymous and hard to block them without blocking the entire network. Login form abuse is mildly irritating but not a huge deal if you have other measures in place. Comment spam is annoying but there are some options that deal with it pretty well.

Then put the form behind your monopolistic internet gatekeeper. There's no reason for a GET to redirect to a sysiphean captcha treadmill.

Re:You don’t want to be on Cloudflare’s naughty list by judge2020 on Tuesday September 20, 2022 @05:49PM (#32918264)
https://blog.cloudflare.com/the-trouble-with-tor/

> . Based on data across the CloudFlare network, 94% of requests that we see across the Tor network are per se malicious. That doesn’t mean they are visiting controversial content, but instead that they are automated requests designed to harm our customers. A large percentage of the comment spam, vulnerability scanning, ad click fraud, content scraping, and login scanning comes via the Tor network. To give you some sense, based on data from Project Honey Pot, 18% of global email spam, or approximately 6.5 trillion unwanted messages per year, begin with an automated bot harvesting email addresses via the Tor network.

Re:You don’t want to be on Cloudflare’s naughty list by remus on Tuesday September 20, 2022 @05:51PM (#32918289)
Say you're running an account take over script that spams login forms with a list of known username and password combos. If a website owner sees thousands of login attempts coming from a single IP address they're likely to block you to prevent abuse on their website. This is annoying for you as you then need to rotate your IP address.

Using tor hides your IP address from the website and makes switching exit nodes very straightforward, so you can run your account take over script in peace.

Re:You don’t want to be on Cloudflare’s naughty list by viraptor on Wednesday September 21, 2022 @07:50AM (#32923697)
That's not that easy in practice. There's less than 2k exits normally, not all of them usable. Your abuse script competed with other malicious traffic for those exits and their reputation gets burned pretty much immediately.

So yes, you can switch exits easily, but effectively your switching from one known bad IP to another bad IP.