Unable to post an answer to a Linux topic, when answer contains certain path names

[Eigenvektor]

Browser, version and OS: 

Firefox (112), Manjaro

 

Steps to reproduce/what were you doing before it happened?

Tried to post an answer to

 

What happened?

Sorry, you have been blocked
You are unable to access linustechtips.com
Why have I been blocked?

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.
What can I do to resolve this?

You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page.

 

What did you expect to happen?

My answer to be posted

 

Any other relevant details:

My original answer contained links to two articles (RedHat and TheGeekDIary) and mentioned the path of the shadow file on Linux as well as the temporary directory. Once I removed these references, I was able to post an answer. I assume mentioning these directories in my examples triggered the issue.

[colonel_mortis]

Both the cloudflare message and the bugs & issues template ask you to include the cloudflare ray id - please can you add that?

[Eigenvektor]

2 hours ago, colonel_mortis said:

Both the cloudflare message and the bugs & issues template ask you to include the cloudflare ray id - please can you add that?

Sorry, failed to copy it the first time around.

 

I reproduced the issue with a test post, here's the ID: 7c07ae251b939a24

 

All I did was create a test post with the content "slash tmp" and "slash etc slash shadow" (replace slash with / and remove the blanks )

[colonel_mortis]

28 minutes ago, Eigenvektor said:

Sorry, failed to copy it the first time around.

 

I reproduced the issue with a test post, here's the ID: 7c07ae251b939a24

 

All I did was create a test post with the content "slash tmp" and "slash etc slash shadow" (replace slash with / and remove the blanks )

Fixed, you can now write /tmp and /etc/shadow without angering the filter.

[HanZie82]

Also, was it not the case when put in CODE tags it would not flag it to begin with.
Like:

/tmp
/etc/shadow

And lets be honest, this looks way better anyway right?!

[Eigenvektor]

21 minutes ago, HanZie82 said:

And lets be honest, this looks way better anyway right?!

Sure, it looks better. But I was just trying to say something along the lines of "You can change your password, even though technically you don't have write access to /etc/shadow". The code block would mostly be a distraction in this case.

[HanZie82]

3 minutes ago, Eigenvektor said:

Sure, it looks better. But I was just trying to say something along the lines of "You can change your password, even though technically you don't have write access to /etc/shadow". The code block would mostly be a distraction in this case.

Lets test


You can change your password, even though technically you don't have write access to /etc/shadow

 

or

 

You can change your password, even though technically you don't have write access to:

/etc/shadow

 

 

 

 

Personally i prefer the 2nd. But to each their own.
Altho changing font on the first one for the path should suffice too imho.

You can change your password, even though technically you don't have write access to /etc/shadow