Checkmk werks level1 July 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
398 discussions

[2.4.0] Checkmk Werk 16441 created: omd cleanup: Remove Version 2.3.0.cee

by Checkmk werks level 1

[//]: # (werk v2) # omd cleanup: Remove Version 2.3.0.cee key | value ---------- | --- date | 2024-07-16T13:04:53+00:00 version | 2.4.0b1 class | fix edition | cre component | omd level | 1 compatible | yes This problem applies to users, which have installed the first released version of Checkmk 2.3.0 (`2.3.0.cee`). Previously, running the command `omd cleanup` would show the following message. ``` 2.3.0.cee Could not determine package. Keeping this version. ``` This meant the corresponding package could not be cleaned up automatically. With this version of OMD, this is done automatically.

1 month, 4 weeks

[2.4.0] Checkmk Werk 16865 created: discovery: Update discovered parameters

by Checkmk werks level 1

[//]: # (werk v2) # discovery: Update discovered parameters key | value ---------- | --- date | 2024-07-19T15:01:34+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes With the rework of `Bulk discovery` and `Periodic service discovery` in 2.3, discovered parameters weren't updated anymore if `Refresh all services and host labels (tabula rasa)` option was used. With this werk, tabula rasa option works like in the version 2.2.

1 month, 4 weeks

[2.3.0] Checkmk Werk 16846 adapted: The custom instances of the MS SQL Server plugin are configured correctly

by Checkmk werks level 1

Werk 16846 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # The custom instances of the MS SQL Server plugin are configured correctly key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p11 class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong key names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # WATO configures correctly custom imstances for MS SQL Server plugin + # The custom instances of the MS SQL Server plugin are configured correctly key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p11 class | fix edition | cee component | checks level | 2 compatible | yes - Previously, configuring custom instances, WATO used wrong names: + Previously, configuring custom instances, WATO used wrong key names: ? ++++ `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package

1 month, 4 weeks

[2.3.0] Checkmk Werk 16846 created: WATO configures correctly custom imstances for MS SQL Server plugin

by Checkmk werks level 1

[//]: # (werk v2) # WATO configures correctly custom imstances for MS SQL Server plugin key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p11 class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package

1 month, 4 weeks

[2.4.0] Checkmk Werk 17129 created: mk_filestats: Apply regex filters while iterating, not afterwards

by Checkmk werks level 1

[//]: # (werk v2) # mk_filestats: Apply regex filters while iterating, not afterwards key | value ---------- | --- date | 2024-07-17T11:33:16+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes

1 month, 4 weeks

[2.4.0] Checkmk Werk 17128 created: mk_filestats: Do not compute file statistics in case of a folder

by Checkmk werks level 1

[//]: # (werk v2) # mk_filestats: Do not compute file statistics in case of a folder key | value ---------- | --- date | 2024-07-16T06:28:13+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes

1 month, 4 weeks

[2.2.0] Checkmk Werk 16886 created: ruleset ewon warning about "Invalid check parameter: Undefined key 'device'.." in UI

by Checkmk werks level 1

Title: ruleset ewon warning about "Invalid check parameter: Undefined key 'device'.." in UI Class: fix Compatible: compat Component: checks Date: 1721369292 Edition: cre Level: 1 Version: 2.2.0p32 The `ewon` ruleset didn't know a `device` key, which was created during recovery, resulting in a warning displayed with the rendered rule in UI saying "Invalid check parameter: Undefined key 'device'..." This change marks `device` as ignored key, satisfying the rule validity check.

2 months

[2.2.0] Checkmk Werk 17013 created: Livestatus injection in mknotifyd

by Checkmk werks level 1

Title: Livestatus injection in mknotifyd Class: security Compatible: compat Component: notifications Date: 1720439889 Edition: cee Level: 1 Version: 2.2.0p32 Before this Werk a malicious notification sent via mknotifyd could allow an attacker to send arbitrary livestatus commands. With this Werk livestatus escaping was added to the relevant functions. This issue was found during internal review. Affected Versions: LI: 2.3.0 LI: 2.2.0 LI: 2.1.0 LI: 2.0.0 (EOL) Vulnerability Management: We have rated the issue with a CVSS Score of 6.5 Medium (<code>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L</code>) and assigned <code>CVE-2024-6542</code>.

2 months

[2.2.0] Checkmk Werk 17150 created: Rename host/item match rule search parameter to clarify behavior

by Checkmk werks level 1

Title: Rename host/item match rule search parameter to clarify behavior Class: fix Compatible: compat Component: wato Date: 1720784196 Edition: cre Level: 1 Version: 2.2.0p32 The rule search page offers two parameters "Host match list" and "Item match list". These parameters could be used to search for rules which have their explicit host or item condition set up in such a way that it matches the given host or service (either by being unset or set). However, these parameters do not check other conditions and might return rules which for other reasons (such as a second host tag condition for example) still might not match the specified host or service. This werk renames these fields to "Explicit host matching" and "Explicit item matching" and expands on their inline help to clarify this behavior. To see which rules are effective on a given host, please refer to the "effective parameters" item under the burger menu in a host monitoring view.

2 months

[2.2.0] Checkmk Werk 17012 created: Check for predefined connections when deploying xinetd config

by Checkmk werks level 1

Title: Check for predefined connections when deploying xinetd config Class: security Compatible: incomp Component: checks Date: 1719818629 Edition: cce Level: 1 Version: 2.2.0p32 When an agent rule Agent controller auto-registration (Managed Services Edition, Cloud Edition) was configured for an agent package one might assume that when installing this package the agent encrypts its traffic. But when installing such a package on a system without systemd but with xinetd installed or a very old systemd versions, the agent was deployed without registration and encryption. With this Werk the deployment script for systemd/xinetd checks for predefined/preconfigured connections and if it finds any it refuses to configure the legacy mode. The agent is still installed though but will not be accessible via the network, so access with SSH will still be possible. Therefore you can no longer use baked packages with auto registration for systems without systemd or very old systemd versions where the legacy mode is desired. These systems need to be excluded from the Agent controller auto-registration (Managed Services Edition, Cloud Edition) rule. Vulnerability Management: We do not rate this as a exploitable vulnerability but a safe guard for unintended configurations, therefore no CVE was assigned. To aid automated scanning we assign a CVSS score of 0.0 None (<code>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N</code>).

2 months

← Newer
1
...
7
8
9
10
11
12
13
...
40
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 July 2024