I have an old SPIP blog (security updates applied with the latest version) on a shared OVHcloud site that is occasionally blocked by the message "Request blocked due to suspicious activity.".
It's very easy to trigger this block; you just need to mention /etc/passwd or any kind of computer code in a plain text textarea (HTML) (I haven't kept track of which other words were censored).
Are you experiencing the same issue?
This kind of censorship that I suspect is generated by AI , is it also applied to you on WordPress or elsewhere? How can one discuss computing topics without being censored? I don't want to waste time encoding such text as I've seen done on censoring platforms (Facebook, etc.).
Finally, what is the purpose of this invasive check in a system that is supposed to be private until the articles are published?
Seriously, OVH has it out for me: I had all sorts of trouble trying to log into this forum even though I was properly logged into the OVH manager. It kept telling me I couldn't log in with my IP address (even though it comes from my French ISP!?)
As for the blocking of my IP address on my website, on Saturday I was also told about a WAF, a term I wasn’t familiar with. I guess it’s the firewall associated with the subdomain’s address.
So I just disabled that firewall for the subdomain linked to the website. And I’m still getting the same IP block from OVHcloud services when I record the characters "/etc/passwd" in a simple text intended to be displayed in a SPIP article.
Definitely, OVH is mad at me: I had all kinds of trouble connecting to this forum even though I was logged in to the OVH manager. It told me I couldn't log in with my IP address (even though it comes from my French ISP!?)
Yes, that happens to me sometimes too, it's still in the testing phase, @FabL aware of that?
As for the blocking of my IP address on my website, on Saturday I was also told about WAF, a term I didn't know. I guess it's the firewall near the sub‑domain's address.
So it's not really a FW in the RZO sense of the term.
I have just disabled this firewall for the sub‑domain linked to the website. And I still get the same IP blocking from OVHcloud services when I record the string "/etc/passwd" in a simple text meant to be displayed in a SPIP article.
So in that case, look rather at SPIP's form sanitization rules.