Owasp-modsecurity-crs: update main GH page to be official website

Created on 15 Jan 2018  路  13Comments  路  Source: SpiderLabs/owasp-modsecurity-crs

In reading the documentation, I started by navigating to https://modsecurity.org/crs from this repository's landing page. However, it seems https://coreruleset.org/ is the official site as it is more recently updated.
If this is the case, could you update the this repository's link to point to the official site? Thanks!

Relates to discussion here:
https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/502

Stale issue

Most helpful comment

Thank you for reporting this @efx. True, that.

@csanders-git, can you do this, or do we need @victorhora / Spiderlabs to perform this for us? It's part of the title (?) when you click on our repository.

All 13 comments

Thank you for reporting this @efx. True, that.

@csanders-git, can you do this, or do we need @victorhora / Spiderlabs to perform this for us? It's part of the title (?) when you click on our repository.

We'll need @victorhora to do this. Their CRS page is outdated and really shouldn't be in use at the top of the page. @victorhora can you please change this?

any update on this @victorhora

Hey @csanders-git, I'm checking if I have rights for this change. I'll get back to you on that.

You should, this is what I think we're talking about

image

We're still waiting on this almost a year later any update @victorhora? Is this the typical response timeline we should expect?

After July 13 passed 76 days or about 3 months and this is about 1/4 of a year. Is this a typical understanding of the calendar we should expect?

Guys, please stop with this passive aggressive tone.

@vladbukin: I appreciate you standing up for Trustwave as is your job. But the request to have our code repository and also modsecurity.org point to our website at https://coreruleset.org is a lot older than this issue. At least a year. And the promise to fix it too.

@csanders-git: I understand your frustration, but let's not vent in public.

@victorhora Any update on this?

I wrote a message to four people at Trustwave. I'll keep you posted.

Another using reporting this and the outdated documentation on modsecurity.org in issue #1482.

And still no fix.

Brought it up on the ModSecurity user mailinglist after the website's cert expired.

This issue has been open 120 days with no activity. Remove the stale label or comment, or this will be closed in 14 days

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dune73 picture dune73  路  6Comments

elexisvenator picture elexisvenator  路  3Comments

ygrek picture ygrek  路  7Comments

franbuehler picture franbuehler  路  5Comments

lifeforms picture lifeforms  路  6Comments