Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update link on Reference Manual v3 wiki page #3136

Open
MefhigosetH opened this issue May 5, 2024 · 2 comments
Open

Update link on Reference Manual v3 wiki page #3136

MefhigosetH opened this issue May 5, 2024 · 2 comments
Assignees
Labels
3.x Related to ModSecurity version 3.x

Comments

@MefhigosetH
Copy link

Describe the bug

The Base64DecodeExt item in the Reference Manual wiki page provide a link that isn't currently online now. I found a version on Internet Wayback machine, and so I want to update this information. But I don't know how to proppose such change, because the Github pages don't support PRs.

To Reproduce

Following the actual link "blog post on Base64Decoding evasion issues on PHP sites" point to http://blog.spiderlabs.com/2010/04/impedance-mismatch-and-base64.html url, that isn't online.

Expected behavior

The link can point to https://web.archive.org/web/20110713164920/http://blog.spiderlabs.com/2010/04/impedance-mismatch-and-base64.html for example.

@MefhigosetH MefhigosetH added the 3.x Related to ModSecurity version 3.x label May 5, 2024
@airween airween self-assigned this May 5, 2024
@airween
Copy link
Member

airween commented May 5, 2024

Hi @MefhigosetH,

thanks for reporting this.

Unfortunately the referred link belongs to an external website that we have no any influence. The other problem is (based on the URI) that page was generated in 2010, so may be it's removed because the owner thought it's too old.

I don't know how correct/polite to put a web.archive.org link into a Wiki page. Any thoughts?

@MefhigosetH
Copy link
Author

MefhigosetH commented May 7, 2024

Dear @airween , thanks for your feedback and sorry for the delay.

I'll check with the last version of ModSecurity if the risk indicated on the website is still valid currently. Give me two days.

If the risk exists, I think the important thing here is document on a paragraph the existence of this risk and maybe (or not), bring the user a link with recommendations about secure use of these functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x Related to ModSecurity version 3.x
Projects
None yet
Development

No branches or pull requests

2 participants