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.
I am seeing the attached whenever I try to edit a blog entry. As I am logged in, I'm not sure why I'm seeing this captcha? (disregard the error, that's not the issue)
Managed to edit without triggering the captcha - had to copy and paste and reconstruct in bits. I had to delete the word "like" from three places in double quotes and the word "having" without the double quotes from one particular sentence. If I added back "having" on a line on it's own in the same entry, the captcha is triggered again.
Is it not possible to turn that kind of invasive and annoying crap off for members who have been registered for a few years / made a certain number of posts?
We skip the vast majority of checks for long time members, but a few happen before we have enough information to make that determination.
--jeremy
I was blocked today too (an hour before). Does (can) it depend on the subforum? Or can it depend on the proxy server I have to use?
And I still blocked, but looks like I can post here.
https://www.linuxquestions.org/quest...0&d=1642669384
^ I have seen this today when replying to a post.
Strangely, it happened only on that 1 tab and only with that 1 reply. I could close & reopen the tab all I wanted, whenever I posted the reply I got that again.
While I had ~10 more LQ tabs open where that didn't happen, I could continue posting there.
I had to disable uBlock completely to even get to the captcha - apparently google-analytics needed its pound of flesh, even though the captcha itself isn't google's.
It makes me sad that this is considered normal nowadays - if I were using a service that does that sort of stuff, my trust in it would be lost.
This is what I posted:
Quote:
Originally Posted by ondoho
deleted because that's what's triggering the captcha, please see here instead
Is there something that triggered the captcha in there? Looks normal to me.
It's a cloudflare issue. I don't think their switching to a new captcha provider is related.
It should not be triggering on words or commands like those regardless.
I don't know how can it be a cloudflare issue:
I could post here, but in the same time another subforum was read only, I could not post anything, because I (my IP) was blocked.
The "security check" can be bypassed by using the full path, escaping/quoting, or ensuring there's a non-L option first - all of which will maintain the (intended) behaviour:
Code:
/bin/ls -l
\ls -l
"ls" -l
ls -1l
A few more quick tests show that the trigger is likely the regex pattern "\nls\s+-l" - i.e. a newline, then "ls" then any number of spaces/tabs/newlines (at least one) then "-l".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.