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

Monthly Chat Agenda April 2024 (2024-03-01 and 2024-04-15) #3636

Closed
dune73 opened this issue Apr 1, 2024 · 2 comments
Closed

Monthly Chat Agenda April 2024 (2024-03-01 and 2024-04-15) #3636

dune73 opened this issue Apr 1, 2024 · 2 comments

Comments

@dune73
Copy link
Member

dune73 commented Apr 1, 2024

This is the Agenda for the two Monthly CRS Chats.

The general chat is going to happen on https://owasp.slack.com in the channel #coreruleset on Monday, 2024-04-01, 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, 2024-04-15. That's the 3rd Monday of the month. Please note that we have a CRS calendar (maintained by @fzipi).

Archived previous meetings and their decision are here.

What happend in the meantime since the chat last month

Outside development

Inside development

Rules

  • FIXME: Please fill in

CRS Sandbox

Security

  • No news on this front.

Plugins

  • FIXME: Please fill in

Documentation and Public Relations

  • We are working on a new version for the website.

Project Administration and Sponsor relationships

  • FIXME: Please fill in

Tools

  • crs-toolchain version 2.2.0 with fixes available.

Testing incl. Seaweed and many future plans

  • No updates on this front.

Containers

  • We are testing the Alpine Apache image using the CIS Benchmark for Apache
  • Now apache and nginx images run using unprivileged users

CRS Status Page

  • No progress

Project discussions and decisions

  • #3623 -> do we want to handle this long accept-encoding header in CRS and allow a value of 100 instead of 50 OR do we say that the user has to write an exclusion rule for this exotic use-case?
  • release policy - we need to update the existing policy to reflect what we are pushing now.
  • Azurit has a series of additional plugins he wants to bet listed or made official. How do we go about this in an effective manner?
  • Hardening of the Apache Alpine docker container according to CIS benchmark (see https://docs.google.com/document/d/1Li2LNSWXSAKOHr5VmO0UgEyMsFQO-Cb915S69GiJ1Lo/edit)

Rules development, key project numbers

PRs that have been merged since the last meeting

We merged 21 PRs since the last monthly project chat.

Open PRs

Open PRs marked DRAFT or work in progress or needs action

Separate 2nd Meeting (Monday, 2024-FIXME)

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.org/slack/invite .

Everybody is welcome to join our community chat.

@fzipi
Copy link
Member

fzipi commented Apr 2, 2024

Decisions April 1

Accept-encoding length
🔵 Decision: looks like going up to 100 will solve the problem reported, and won't break anything. So we decided to go 100.

Release Policy
🔵 Decision: @fzipi will create a new drive document so we can start collaborating on a policy document.

Plugin adoption
🔵 Decision: @azurit will create a new PR template with the steps for plugins to be accepted using https://github.com/coreruleset/coreruleset/wiki/New-plugin-creation-and-integration as base.

@franbuehler
Copy link
Contributor

franbuehler commented Apr 15, 2024

Decisions April 15

OWASP summit / CRS retreat
🔵 Decision: CRS would participate the official OWASP summit as a project. We hope for some exchange with other projects, but we really want to work on CRS as productively as possible.

Mozlila User Agent
🔵 Decision: We want to block this. We don't see it as legitimate.

Disable FW prevention
🔵 Decision: no agreement on this question tonight. We need more time to think about this and then take it into the Agenda in May.

Axel
🔵 Decision: @theseion will take a look and @franbuehler will help

CIS Benchmark for Apache Docker Container
🔵 Decision: Everything that can not obviously be exploited should be left as per default because anything we change we will have to maintain. @dune73 will try to get the low hanging fruits sorted and then maybe add documentation to talk about hardening.

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

4 participants