Branch: refs/heads/2.0.0 Home: https://github.com/tribe29/checkmk Commit: 07ac6998ea501a47563b1954252d251373120a61 https://github.com/tribe29/checkmk/commit/07ac6998ea501a47563b1954252d25137… Author: Ronny Bruska <ronny.bruska(a)tribe29.com> Date: 2021-04-28 (Wed, 28 Apr 2021) Changed paths: A .werks/12751 M cmk/gui/plugins/views/icons/mkeventd.py A tests/unit/cmk/gui/plugins/views/icons/test_icon_mkeventd.py Log Message: ----------- 12751 FIX mkevents: Fix link to events of host FEED-6006 Change-Id: I85cf5bd04731f7658d4aff153b5f56ffb66fb069 Commit: 3a5bd1efc6943880c927a82d45005dc49be74ba2 https://github.com/tribe29/checkmk/commit/3a5bd1efc6943880c927a82d45005dc49… Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com> Date: 2021-04-28 (Wed, 28 Apr 2021) Changed paths: A .werks/12672 M agents/check_mk_agent.linux Log Message: ----------- 12672 SEC real-time-checks: Provide default password This Werk fixes a security issue that may arise from a misconfiguration of real-time checks. As mentioned in Werk #8350 (Introduction of real-time checks), a password has to be provided when configuring real-time checks. When using the agent bakery, the ruleset "Encryption" is used to provide the encryption password, while the real-time checks itself are activated for the agents via the ruleset "Send data for real-time checks". If the real-time checks get activated without providing a password, this will result in an empty password, that will nevertheless be used by the agent to encrypt the real-time check data on the host. While the user would most likely fix this situation, because real-time checks won't work (A password is mandatory to activate real-time checks in CMC), the real-time check data can be decrypted without a password/key in this case, resulting in a security issue. This is now fixed with the following mechanism: - The agent bakery will read the default password from the global setting "Monitoring core/Enable handling of real-time checks" and bake it into the agents that have the rule "Send data for real-time checks" activated. Accordingly, a changed global setting will lead to new agents on next bake. - The agent bakery will keep to package the password from the "Encryption" rule, and the Linux agent will prefer it over the default password from the CMC configuration. - If none of the two passwords are configured, but the "Send data for real-time checks" rule is active, the agent bakery will refuse to bake agents - If the Linux agent is requested to send encrypted real-time check data, but no password is deployed, no real-time check data will be sent. However, up from now, this may only happen if real-time checks are configured without the agent bakery. CMK-7590 Change-Id: I977f4acede5bacaad376cad08bc485e1a58981db Compare: https://github.com/tribe29/checkmk/compare/f25f9fdaa92f...3a5bd1efc694