Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15969 discussions

Checkmk Werk 14482: Use proper HMAC for cookie signing

by Maximilian Wirtz

ID: 14482 Title: Use proper HMAC for cookie signing Component: Setup Level: 1 Class: Security fix Version: 2.2.0i1 Previously to this Werk the Session cookies were signed with with calculating a SHA256 hash over username, session id, a serial plus a secret. This could in theory lead to a "partial message collision". Since we parse the data given in the cookie and test for validity, we are confident that such an attack is not possible. But to be future-proof we switch to proper HMAC for signing the cookie value. This will invalidate all session cookies for a site. Therefore all users have to reauthenticate to retrieve new valid cookies.

2 years

Checkmk Werk 14719: Local customizations might need adjustment due refactorings in GUI code (<tt>PasswordFromStore</tt>)

by Joerg Herbel

ID: 14719 Title: Local customizations might need adjustment due refactorings in GUI code (<tt>PasswordFromStore</tt>) Component: Setup Level: 1 Class: New feature Version: 2.2.0i1 This werk only affects users of non-tribe29 local customizations (single files and MKPs from non- tribe29 sources such as the Checkmk exchange). Before this werk, the Checkmk codebase offered two convenience functions for creating <tt>ValueSpecs</tt> for passwords (either entered directly or selected from the password store): <tt>IndividualOrStoredPassword</tt> and <tt>PasswordFromStore</tt>. These two functions had misleading names and were therefore renamed: LI: <tt>IndividualOrStoredPassword</tt> was renamed to <tt>TransformToIndividualOrStoredPassword</tt>, because this actually reflects what the returned <tt>ValueSpec</tt> does: It allows users to either directly enter a password or select one from the store. Furthermore, it also handles legacy configurations which did not offer the option to use the password store. LI: <tt>PasswordFromStore</tt> was renamed to <tt>IndividualOrStoredPassword</tt>, which also reflects its purpose: either directly enter a password or to select one from the store, but without the handling of legacy configurations. To stay compatible, we recommend to simply use <tt>IndividualOrStoredPassword</tt> instead of <tt>PasswordFromStore</tt> in Checkmk 2.1 customizations, which will continue working when upgrading to 2.2. Note that this only affects non-tribe29 customizations because as of the writing of this werk, any customization produced by tribe29 will be obsolete with Checkmk 2.2.

2 years, 1 month

Checkmk Werk 14676: Item description in CheckParameterRuleSpecWithItem mandatory

by Max Linke

ID: 14676 Title: Item description in CheckParameterRuleSpecWithItem mandatory Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 This change might break existing MKPs. When writing a new rulespec for a check with an item the item_spec could be left blank. However those are needed to properly render the rulespec and allow to enable a rulespec only for specific services of a check plugin. Now the item_spec parameter is mandatory. The item_name, and item_help parameters have been removed, with werk #14677. Below is an example how to register a new rulespec for a check with an item. C+: rulespec_registry.register( CheckParameterRulespecWithItem( check_group_name="a_check", item_spec=lambda: TextInput(title="fitting item name", help="inline help text"), group=RulespecGroupCheckParametersApplications, parameter_valuespec=_parameter_valuespec_network, title=lambda: "A good title", ) ) C-:

2 years, 1 month

Checkmk Werk 14782: Monitor systemd sockets as summary services

by Timotheus Bachinger

ID: 14782 Title: Monitor systemd sockets as summary services Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 With this werk, a new summary check (corresponding to Systemd Service Summary) is available.

2 years, 1 month

Checkmk Werk 14781: Monitor systemd sockets as single services

by Timotheus Bachinger

ID: 14781 Title: Monitor systemd sockets as single services Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 Previously, Systemd's services could be monitored as single service only. With this werk, Systemd's sockets can be monitored as a single check, similar to Systemd's services.

2 years, 1 month

Checkmk Werk 14731: super_server: Reenable "Checkmk agent network service (Linux)" ruleset

by Andreas Umbreit

ID: 14731 Title: super_server: Reenable "Checkmk agent network service (Linux)" ruleset Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 This is a regression since Checkmk 2.1. The agent package install scripts didn't recognize the <tt>/etc/check_mk/super_server.cfg</tt> correctly. As a result, the super server, if configured other than "auto", wasn't set correctly. In order to apply this fix, an agent update or reinstallation has to be done on affected hosts.

2 years, 1 month

Checkmk Werk 13019: Update requests module

by Konstantin Baikov

ID: 13019 Title: Update requests module Component: config Level: 1 Class: Bug fix Version: 2.2.0i1 Update requests module to fix an upstream bug with proxy authentication. Fixed parsing issue that resulted in the auth component being dropped from proxy URLs. (#6028)

2 years, 1 month

Checkmk Werk 14801: Improve detection when OMD runs in a container

by External contributor

ID: 14801 Title: Improve detection when OMD runs in a container Component: Site Management Level: 1 Class: Bug fix Version: 2.2.0i1 Only for docker and podman we could reliably detect if OMD is running in a container. The official docker image now sets a CMK_CONTAINERIZED=TRUE environment variable that is checked in omd. This works independent of the container runtime used.

2 years, 1 month

Checkmk Werk 14610: super_server: Missing systemd units/xinetd services after agent update (RPM)

by Andreas Umbreit

ID: 14610 Title: super_server: Missing systemd units/xinetd services after agent update (RPM) Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 After agent update to a 2.1 linux agent (prepackaged and bakery versions) on RPM based systems, the agent installation may end up with missing systemd units or a missing xinetd service file. As a workaround, or to recover from an agent installtion with broken super-server, agents can be reinstalled once manually with <tt>cmk-update-agent --reinstall</tt> or <tt>cmk-update-agent --force</tt> to restore the missing file(s). Subsequent agent updates won't run into the same problem again. With this Werk, the initial agent update to version 2.1 won't run into the problem in the first place.

2 years, 1 month

Checkmk Werk 14609: super_server: Cleanup config files when installing a bakery package

by Andreas Umbreit

ID: 14609 Title: super_server: Cleanup config files when installing a bakery package Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 This Werk will be compatible for most users. See below for details. When using the prepackaged agent package on DPKG or RPM based systems, some xinetd/system files are marked as config files and won't be removed on uninstallation/update. This leads to problems when updating from a prepackaged agent package to a bakery agent package, as leftover service or unit files would occupy the listening agent port. Bakery agent packages will now remove all deprecated systemd/xinetd files that may be leftover from old installations before activating the new super server coming from the new package. Please be aware that, starting with this Werk, agent packages from the agent bakery will discard changes made to xinetd/systemd files from a previously installed prepackaged/raw edition agent package. While this is expected behavior for bakery packages, it may still change some agent installations in an unexpected way, because this was done inconsequently in the past.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1