8000 Monthly Chat Agendas February (2021-02-01 and 2021-02-15) · Issue #1992 · coreruleset/coreruleset · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Monthly Chat Agendas February (2021-02-01 and 2021-02-15) #1992

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

Closed
dune73 opened this issue Jan 27, 2021 · 1 comment
Closed

Monthly Chat Agendas February (2021-02-01 and 2021-02-15) #1992

dune73 opened this issue Jan 27, 2021 · 1 comment

Comments

@dune73
Copy link
Member
dune73 commented Jan 27, 2021

This is the Agenda for the Monthly CRS Chats.

The general chat is going to happen on https://owasp.slack.com in the channel #coreruleset on Monday, February 1st, at 20:30 CET. That's the 1st Monday of the month. A separate issue chat is happening at the same location, same time on Monday, February 15th. That's the 3rd Monday of the month.

Items on the Agenda: (see previous meetings decisions: here)

What happend in the meantime since the chat last month

Outside development

  • Wallarm published a repo with an automatic test to detect CRS bypasses: Link
  • The wiki has a link to issues / PRs assigned to every CRS developer
  • Blog post Introducing msc_retest - a tool set to do performance testing of regex execution speed on various ModSec versions

PRs that have been merged since the last meeting

Open PRs

Open PRs marked "work in progress" / needs action

Other items

  • Python 2.7 deprecated (see feat(ci): use relative paths in testing #1936 (review))
  • Special topic* : Blogpost about the ModSec3 security problem with disabling request body access.
  • Talking about the 3.4 release
  • Idea to allow for plugins: So that's rule sets outside the main CRS releases with rules that we or 3rd parties develop
    • This would allow for rules that are somewhat out of scope for us
    • This would allow for 3rd parties to integrate with anomaly scoring more easily
    • This would allow for the use of more advanced features (-> Lua!) without limiting CRS integration with more dependencies
    • This would allow these rule sets to follow their own release rhythm (right now, such additional rule sets will only be updated when we do a major release

Open Issues - Separate Issues Meeting (Monday, February 15th)

We generally cover 10 issues per month in a separate issue meeting. Add them as you see fit.

How to get to our slack and join the meeting?

If you are not yet on the OWASP Slack, here is your invite: https://owasp-slack.herokuapp.com/ .

Everybody is welcome to join our community chat.

@franbuehler
Copy link
Contributor
franbuehler commented Feb 1, 2021

Decisions

PRs

Other items

  • For FTW tests we still depend on py2 which will no longer be supported. @fzipi is working on a Go port: https://github.com/fzipi/go-ftw.
  • Release 3.4 was scheduled 3.4 for Feb / March but after the last meeting more problems with the early blocking on ModSec3 popped up. We have to wait for a couple of weeks...

Open Issues - Separate Issues Meeting (Monday, February 15th)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0