Re:You don’t want to be on Cloudflare’s naughty list
by d2wa on Tuesday September 20, 2022 @12:49PM
(#32914421)
(Author here.) That’s missing from the article. But I have logs of the network. There’s nothing out of the ordinary. “I don’t know what I did wrong,” as I started the article, means “I’ve checked logs and such and there’s no indication of anything wrong on my end.”
Re:You don’t want to be on Cloudflare’s naughty list
by JohnFen on Tuesday September 20, 2022 @05:55PM
(#32918326)
A task that would be made much easier and less likely to miss something if the affected person had some indication as to what the problem was.
Re:You don’t want to be on Cloudflare’s naughty list
by buildbot on Tuesday September 20, 2022 @06:06PM
(#32918449)
Devil's advocate - would it not then be pretty easy to engineer malicious bots to avoid detection?
Re:You don’t want to be on Cloudflare’s naughty list
by JohnFen on Tuesday September 20, 2022 @07:11PM
(#32918998)
Depends on the level of detail provided. That much detail isn't necessary in order to provide a helpful pointer to innocent bystanders.
Re:You don’t want to be on Cloudflare’s naughty list
by Ferret7446 on Tuesday September 20, 2022 @11:59PM
(#32920702)
Do you expect the average user to know how to "eliminate the possibility that a device on their network is compromised"? That is untenable.
Re:You don’t want to be on Cloudflare’s naughty list
by mh- on Wednesday September 21, 2022 @12:05AM
(#32920719)
No, but I wouldn't expect the average user to write a blog post with unsubstantiated technical claims, either.
I do think Cloudflare could do better here to let the owner of an IP know why they're suffering from poor reputation.
However, it's not immediately clear to me how they could accomplish this without weakening their side of the car vs. mouse game.
That person should start with the assumption they haven't been misclassified and eliminate the possibility that a device on their network is compromised.