Actions
Bug #1114
closedmissing config info
Affected Versions:
Effort:
Difficulty:
Label:
Description
suricata --dump-config
does not show all options. Example
app-layer.protocols.http.enabled = yes app-layer.protocols.http.libhtp = (null) app-layer.protocols.http.libhtp.default-config = (null) app-layer.protocols.http.libhtp.default-config.personality = IDS app-layer.protocols.http.libhtp.default-config.request-body-limit = 3072 app-layer.protocols.http.libhtp.default-config.response-body-limit = 3072 app-layer.protocols.http.libhtp.default-config.request-body-minimal-inspect-size = 32kb app-layer.protocols.http.libhtp.default-config.request-body-inspect-window = 4kb app-layer.protocols.http.libhtp.default-config.response-body-minimal-inspect-size = 32kb app-layer.protocols.http.libhtp.default-config.response-body-inspect-window = 4kb app-layer.protocols.http.libhtp.default-config.double-decode-path = no app-layer.protocols.http.libhtp.default-config.double-decode-query = no app-layer.protocols.http.libhtp.server-config = (null)
there should be a line with
app-layer.protocols.http.memcap = 32
The same with
app-layer.protocols.dns
Updated by Victor Julien about 10 years ago
- Assignee set to Jason Ish
- Target version set to TBD
Jason, can you check this?
Updated by Jason Ish about 10 years ago
It seems to work for me.
The default suricata.yaml has app-layer.protocols.http.memcap commented out, so it does not appear in --dump-config, which is really just an internal representation of what was parsed from the configuration file. It does not take into consideration the hard coded defaults.
If this is still a problem, can you share your suricata.yaml?
Updated by Peter Manev about 10 years ago
- Status changed from Assigned to Closed
This is correct.
Thanks for the info Jason.
Not a bug.
Actions