Checkmk werks level1 September 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
142 discussions

[2.3.0] Checkmk Werk 17167 created: HTML Email: Add from address to log on SMTP error

by Checkmk werks level 1

[//]: # (werk v2) # HTML Email: Add from address to log on SMTP error key | value ---------- | --- compatible | yes version | 2.3.0p15 date | 2024-09-02T12:52:58+00:00 level | 1 class | fix component | notifications edition | cre

2 weeks, 2 days

[2.3.0] Checkmk Werk 17166 created: HTML Email: Handle SMTP return code 554 as permanent error

by Checkmk werks level 1

[//]: # (werk v2) # HTML Email: Handle SMTP return code 554 as permanent error key | value ---------- | --- compatible | yes version | 2.3.0p15 date | 2024-09-02T12:48:22+00:00 level | 1 class | fix component | notifications edition | cre If you used "Enable synchronous delivery via SMTP" the return code 554 was not handled as a permanent error, leading to multiple delivery attempts. This return code is now handled as permanent error.

2 weeks, 2 days

[2.3.0] Checkmk Werk 16594 adapted: Container: Support setting custom timezone

by Checkmk werks level 1

Werk 16594 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Container: Support setting custom timezone key | value ---------- | --- date | 2024-08-21T15:44:20+00:00 version | 2.3.0p14 class | feature edition | cre component | packages level | 1 compatible | yes The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use. The timezone information is then set for the site running inside the container. This removes the need to mount timezone files from the host machine into a docker container. A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Container: Support setting custom timezone key | value ---------- | --- date | 2024-08-21T15:44:20+00:00 version | 2.3.0p14 class | feature edition | cre component | packages level | 1 compatible | yes The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use. The timezone information is then set for the site running inside the container. This removes the need to mount timezone files from the host machine into a docker container. + A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>`

2 weeks, 2 days

[2.3.0] Checkmk Werk 16997 created: NagVis: Updated to 1.9.43

by Checkmk werks level 1

[//]: # (werk v2) # NagVis: Updated to 1.9.43 key | value ---------- | --- date | 2024-08-30T07:45:48+00:00 version | 2.3.0p15 class | fix edition | cre component | packages level | 1 compatible | yes

2 weeks, 2 days

[2.4.0] Checkmk Werk 16997 adapted: NagVis: Updated to 1.9.43

by Checkmk werks level 1

Werk 16997 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # NagVis: Updated to 1.9.43 key | value ---------- | --- date | 2024-08-30T07:45:48+00:00 version | 2.4.0b1 class | fix edition | cre component | packages level | 1 compatible | yes ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # NagVis: Updated to 1.9.43 key | value ---------- | --- date | 2024-08-30T07:45:48+00:00 - version | 2.3.0p14 ? ^ ^ - + version | 2.4.0b1 ? ^ ^ class | fix edition | cre component | packages level | 1 compatible | yes

2 weeks, 2 days

[2.4.0] Checkmk Werk 16566 created: Standardize notification spooler log level configuration

by Checkmk werks level 1

[//]: # (werk v2) # Standardize notification spooler log level configuration key | value ---------- | --- date | 2024-09-02T09:16:08+00:00 version | 2.4.0b1 class | fix edition | cee component | notifications level | 2 compatible | yes The notification spoolers log level was configured differently than other services. Previously users had the choice between: * Normal logging (only startup, shutdown and errors) * Verbose logging (also spooled notifications) * Debugging (log every single action) This was changed to the standard log levels which we also use in all other services. The command line flag `-v` of the `mknotifyd`, which could be used to override the configured log level was replaced with the `--log-level=LEVEL` argument. While the change to this command line flag is an incompatible change, we don't rate this as a change that is worth marking the werk to be incompatible. In the end it's only an option used for manual debugging.

2 weeks, 2 days

[2.4.0] Checkmk Werk 17167 created: HTML Email: Add from address to log on SMTP error

by Checkmk werks level 1

[//]: # (werk v2) # HTML Email: Add from address to log on SMTP error key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-09-02T12:52:58+00:00 level | 1 class | fix component | notifications edition | cre

2 weeks, 2 days

[2.4.0] Checkmk Werk 17166 created: HTML Email: Handle SMTP return code 554 as permanent error

by Checkmk werks level 1

[//]: # (werk v2) # HTML Email: Handle SMTP return code 554 as permanent error key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-09-02T12:48:22+00:00 level | 1 class | fix component | notifications edition | cre If you used "Enable synchronous delivery via SMTP" the return code 554 was not handled as a permanent error, leading to multiple delivery attempts. This return code is now handled as permanent error.

2 weeks, 2 days

[2.4.0] Checkmk Werk 16594 adapted: Container: Support setting custom timezone

by Checkmk werks level 1

Werk 16594 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Container: Support setting custom timezone key | value ---------- | --- date | 2024-08-21T15:44:20+00:00 version | 2.4.0b1 class | feature edition | cre component | packages level | 1 compatible | yes The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use. The timezone information is then set for the site running inside the container. This removes the need to mount timezone files from the host machine into a docker container. A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Container: Support setting custom timezone key | value ---------- | --- date | 2024-08-21T15:44:20+00:00 version | 2.4.0b1 class | feature edition | cre component | packages level | 1 compatible | yes The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use. The timezone information is then set for the site running inside the container. This removes the need to mount timezone files from the host machine into a docker container. + A run command can look like this: `docker container run ... --env TZ="Europe/Berlin" check-mk-enterprise:<version>`

2 weeks, 2 days

[2.3.0] Checkmk Werk 17148 created: Persist known host keys for checks that use SSH

by Checkmk werks level 1

[//]: # (werk v2) # Persist known host keys for checks that use SSH key | value ---------- | --- date | 2024-08-26T08:56:04+00:00 version | 2.3.0p14 class | security edition | cre component | checks level | 1 compatible | yes When using the special agent *VNX quotas and filesystems* or the active check *Check SFTP Service* the host keys were not properly checked. If an attacker would get into a machine-in-the-middle position he could intercept the connection and retrieve information e.g. passwords. As of this Werk the host key check is properly done. In order to store known host keys a regular `known_hosts` file is used that is stored in `/omd/sites/$SITENAME/.ssh/known_hosts`. If a host key changes an error is now raised that requires manual edit of this file. This issue was found during internal review. *Affected Versions*: * 2.3.0 * 2.2.0 * 2.1.0 * 2.0.0 (EOL) *Vulnerability Management*: We have rated the issue with a CVSS Score of 6.3 Medium CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N and assigned CVE-2024-6572.

2 weeks, 3 days

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2024