LQ needs to review the security of your connection frustrating delays
LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: native install of Parrot Home Edition 5.0 Debian (no security tools) 64 bit, KDE, 5.14.0-9parrot1,
Posts: 872
Rep:
LQ needs to review the security of your connection frustrating delays
I am getting a lot delays from this (below):
It's getting really bad, this never happened years ago when visiting LQ with tor browser. Can something be done about it?
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,506
Rep:
No delays for me either - very rarely I get an 'unreachable', but so far & few between, that I just go to another site first, then come back here without any further 'problem'.
Moved: This thread is more suitable in Suggestions and Feedback and has been moved accordingly to help your thread/question get the exposure it deserves.
That looks a bit like some of the Cloudflare capcha requirements that people used to get if they posted code containing certain commands. There's a thread on it somewhere.
Distribution: native install of Parrot Home Edition 5.0 Debian (no security tools) 64 bit, KDE, 5.14.0-9parrot1,
Posts: 872
Original Poster
Rep:
Quote:
Originally Posted by hazel
That looks a bit like some of the Cloudflare capcha requirements that people used to get if they posted code containing certain commands. There's a thread on it somewhere.
Commands contained with the 'submit reply'?It occurs for minutes on end even without submitting commands within a reply,like for instance clicking page 2 of a thread. Why is there a need for Cloudfare? Is LQ a site where nefarious actors gravitate?
I believe, it is. So I should just not utter a word about it – sorry. But there is a lot of work done just to allow the idiots to disappear. From our eyes, at least.
Distribution: native install of Parrot Home Edition 5.0 Debian (no security tools) 64 bit, KDE, 5.14.0-9parrot1,
Posts: 872
Original Poster
Rep:
I haven't been able to access the forum properly for weeks because of Cloudfare. I was getting the same Cloudfare message, and couldn't even get though to main home page to log in most times, and if I did, when a post was clicked, Cloudfare blocked. I am on tor. Appears to be working now, but for how long?
It blocks regardless of whether you embedded code into your post or not.
Apparently Cloudflare doesn't like people using tor. That in itself seems suspicious to me. What kind of people object to other people wanting more privacy?
Apparently Cloudflare doesn't like people using tor. That in itself seems suspicious to me. What kind of people object to other people wanting more privacy?
When you use TOR to access regular (non-onion) websites, you're using somebody's TOR exit node. Unfortunately, so is everybody else and his dog. The likelihood of some nefarious activity originating from that same IP address at any one time is pretty high, which is probably what's triggering CloudFlare's protection mechanisms.
If LQ had an .onion address that could be accessed directly via TOR, this wouldn't be an issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.