Andrea Selva
Andrea Selva
Hi @skumarp7 please send an email to [email protected] communicating which CVE this PR is trying to fix, in the email please specify to communicate with the Logstash team 🙏
Thanks @kaisecheng for your review, added the allow.legacy.monitoring flag to BK pipeline and now logs a warn when legacy monitoring is enabled and not allowed. Example of line logged: ```...
@kaisecheng > ☝️ Almost there was fixed in https://github.com/elastic/logstash/pull/16586/files#diff-a0255510e1f939e6ad6e719d7db5ec42a9f0e886171561b1084da93693a44256R6 if I'm not wrong
@karenzone yes it's related just to the internal collector. Do you thing we should switch naming from `allow.legacy.monitoring` to `allow.internal.legacy.monitoring` ?
@logstashmachine backport 8.17
@logstashmachine backport 8.16
8.17: ~~https://github.com/elastic/logstash/pull/16947~~ https://github.com/elastic/logstash/pull/16960 8.16: ~~https://github.com/elastic/logstash/pull/16948~~ https://github.com/elastic/logstash/pull/16961
@logstashmachine backport 8.x
`8.x` backport https://github.com/elastic/logstash/pull/16959
I'll check this, but from MQTT specification http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html : ``` If the Server receives a QoS 0 message with the RETAIN flag set to 1 it MUST discard any message...