Documentation #7222
openDocumentation #3180: tracking: document all decoder and app-layer events
userguide: document decoder events
Description
We have several rules shipped with Suricata (under the rules directory), but those aren't documented.
This task consists of documenting the decoder events seen in the rules present in the decoder-events.rules file.
This document should be named decoder-events.rst and should be a section of a sub-chapter of the Suricata Rules chapter in our Userguide. Please ask us (or suggest) what the name of that sub-chapter should be. One suggestion is Event rules provided with Suricata
Userguide
- Suricata Rules (chapter)
- Rules Shipped with Suricata (sub-chapter)
- Decoder events (chapter section)
- Rules Shipped with Suricata (sub-chapter)
Updated by Juliana Fajardini Reichow over 1 year ago
- Related to Documentation #7223: document 'stream-event' keyword added
Updated by Ezra Adeyinka about 1 month ago
- Assignee changed from Community Ticket to Ezra Adeyinka
Picking this up!
Updated by Juliana Fajardini Reichow about 1 month ago
- Status changed from New to Assigned
Updated by Juliana Fajardini Reichow 17 days ago
- Assignee changed from Ezra Adeyinka to Community Ticket
- Label deleted (
Outreachy)
Hi there, according to our guidelines for stale tickets, I'm un-assigning this ticket.
Thanks for your interest in our project, and feel free to reach out in case you have time and want to contribute to Suricata again :) :)
Refer to:
https://forum.suricata.io/t/important-outreachy-contribution-phase-wrap-up-prs-claimed-tickets-and-more
https://docs.suricata.io/en/latest/devguide/codebase/contributing/contribution-process.html#stale-tickets-policy