Checkmk werks level1 February 2022

checkmk-werks-lvl1@lists.checkmk.com

21 participants
74 discussions

Checkmk Werk 13614: Fix missing context in title on hostgroup and servicegroup views

by Óscar Nájera

ID: 13614 Title: Fix missing context in title on hostgroup and servicegroup views Component: Multisite Level: 1 Class: Bug fix Version: 2.1.0i1

2 years, 7 months

Checkmk Werk 13664: Fix required comment field on removing of downtimes

by Ronny Bruska

ID: 13664 Title: Fix required comment field on removing of downtimes Component: Multisite Level: 1 Class: Bug fix Version: 2.1.0i1 If downtimes were removed, a comment entry was required. This has been changed to optional because for removements of downtimes, no comment is necessary.

2 years, 7 months

Checkmk Werk 13092: Fixed types of various CMC Livestatus columns

by Sven Panne

ID: 13092 Title: Fixed types of various CMC Livestatus columns Component: Livestatus Level: 1 Class: Bug fix Version: 2.1.0i1 NOTE: If you don't query some of the more esoteric Livestatus columns in your own scripts, plugins, etc., you don't have to do anything. If you do, read on... Some Livestatus columns had a wrong type when the CMC was used, and those types were inconsistent with the corresponding Livestatus colulmns when the Nagios Core was used. The CMC column types have been fixed now, in detail: The "x_3d", "y_3d", "z_3d" columns of hosts have the correct type "double" now, previously they were a "string". The "last_command_check" column of the status table has type "time" now, previously it was a "string".

2 years, 7 months

Checkmk Werk 13633: The password store is now storing passwords obfuscated

by Lars Michelsen

ID: 13633 Title: The password store is now storing passwords obfuscated Component: Core & setup Level: 2 Class: New feature Version: 2.1.0i1 The password stores primary use is to centralize stored credentials. Instead of spreading the credentials in the whole configuration, we have this as a central place for sensitive information. We are a monitoring system. We definitely need credentials in clear text to contact remote some systems all the time. And we also need to be able do this after restarting the whole system without user interaction (for providing some kind of master key). This means the secrets need to be available to the site user on disk in clear text. To underline this fact, we kept the password store file in clear text on disk for a long time. This approach made the situation clearly visible to everyone. We are faced with the requirement that no credential shall be stored in clear text on disk, they need to be encrypted. We'd love to have that too. But since securing is not possible, we are now "obfuscating". In fact it's encryption, but we are doing it with a secret that is stored in the same context as the password store itself - this is why we call it obfuscation. The best we can do in this case. With the development of Checkmk 2.2 we will evaluate the usage of HSMs as well as vault solutions in the future which may be helpful in some use cases. The password store file <tt>var/check_mk/stored_passwords</tt> is now encrypted using the new password store key (<tt>etc/password_store.secret</tt>). This key is created during update to Checkmk 2.1 automatically. You are free to replace the secret with what ever text you want. But please note that the password store needs to be initialized again after changing the secret. All existing passwords stores will be obfuscated automatically during update to Checkmk 2.1.

2 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 February 2022