| Summary: | DNS resolvers should be placed in DNS_SERVERS in suricata.yaml | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Peter Müller <peter.mueller> |
| Component: | --- | Assignee: | Stefan Schantl <stefan.schantl> |
| Status: | CLOSED FIXED | QA Contact: | Peter Müller <peter.mueller> |
| Severity: | Security | ||
| Priority: | Will affect most users | CC: | arne.fitzenreiter, michael.tremer |
| Version: | 2 | Keywords: | Security |
| Hardware: | all | ||
| OS: | All | ||
| See Also: | https://bugzilla.ipfire.org/show_bug.cgi?id=12260 | ||
| Bug Depends on: | |||
| Bug Blocks: | 12052 | ||
|
Description
Peter Müller
2019-09-05 17:33:05 UTC
Since observing DNS traffic from or to the resolvers as such might have security implications, I am changing the priority of this. Yes I agree. Stefan, please make this a priority. Patchset has been sent to the development mailing list: https://patchwork.ipfire.org/patch/2573/ https://patchwork.ipfire.org/patch/2574/ https://patchwork.ipfire.org/patch/2575/ https://patchwork.ipfire.org/patch/2576/ https://patchwork.ipfire.org/patch/2577/ In order to ship this changes by a core update the changed files needs to be shipped and the red.up suricata script needs to be launched . |