[//]: # (werk v2)
# disk_smb: Allow macros in 'NetBIOS name of the server' field
key | value
---------- | ---
compatible | yes
version | 2.3.0p5
date | 2024-05-28T11:21:20+00:00
level | 1
class | fix
component | checks
edition | cre
With the rework of disk_smb active check in version 2.1.0, using macros in
'NetBIOS name of the server' was disallowed. Now, the macros are enabled
for this field again.
[//]: # (werk v2)
# mk-sql adds headers to the error message
key | value
---------- | ---
date | 2024-05-28T16:36:29+00:00
version | 2.3.0p4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously, the mk-sql plugin would send only error text when
an error occurred, which could disrupt other services.
Now, in the event of an error, the mk-sql plugin always sends
SQL plain headers, thereby eliminating this problem.
[//]: # (werk v2)
# Restrict check_sftp local paths
key | value
---------- | ---
date | 2024-05-16T09:48:20+00:00
version | 2.3.0p4
class | security
edition | cre
component | checks
level | 1
compatible | no
Prior to this Werk, `check_sftp` did not restrict the local paths that for files to be uploaded and downloaded.
This allowed users with the permissions to configure `check_sftp` to read or write files within the Checkmk site home.
The local paths are now restricted to the folder `var/check_mk/active_checks/check_sftp` within the Checkmk site home.
As a consequence, the local paths in existing configurations will now be interpreted as relative to that folder.
Since a test file is created if the local file to upload doesn't exist, the check will continue to work, but it will not pick up files from the old location.
Similarly, the downloaded files will be stored in a new location.
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 8.8 High with the following CVSS vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` and assigned CVE `CVE-2024-28826`.
[//]: # (werk v2)
# HW/SW inventory: syncing inventory data from remote to central site did not work
key | value
---------- | ---
compatible | yes
version | 2.3.0p4
date | 2024-05-28T08:33:44+00:00
level | 1
class | fix
component | inv
edition | cre
HW/SW data synchronisation between a remote and a central site was interrupted after a new host was introduced at the remote site.
[//]: # (werk v2)
# Show timeout in failed notifications
key | value
---------- | ---
compatible | yes
version | 2.3.0p4
date | 2024-05-27T09:57:30+00:00
level | 1
class | fix
component | notifications
edition | cee
If a notification process was terminated because of a timeout, in the failed
notifications view only "HOST/SERVICE NOTIFICATION RESULT" was shown without
further informations.
We now show the current delivery attempt and the timeout in seconds.
You will find this message also in the notify.log next to the spoolfile name.
[//]: # (werk v2)
# Dashboard element "Average scatterplot": Fix topmost rendering
key | value
---------- | ---
date | 2024-05-21T07:16:13+00:00
version | 2.3.0p4
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
The dashboard element "Average scatterplot" was rendered topmost at all times after being hovered once. This resulted in other dashboard elements' tooltips to be rendered behind the "Average scatterplot" element.
This behavior is fixed. After hovering the "Average scatterplot", i.e. when moving the mouse outside of its graph area, its topmost rendering is reset, making other tooltips visible again.
[//]: # (werk v2)
# Use correct proxy settings for plugin "SMS (using modern API)"
key | value
---------- | ---
date | 2024-05-27T10:57:53+00:00
version | 2.3.0p4
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
If you used HTTPS for the modem URL, a ProxyError was raised on execution.
Workaround was to use HTTP.
[//]: # (werk v2)
# Ruleset API: Fix KeyError for nested form_specs.DictGroup
key | value
---------- | ---
date | 2024-05-23T09:54:29+00:00
version | 2.3.0p4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This is only relevant for plugin developers.
In some cases when a `DictGroup` was used inside a FormSpec hierarchy an error would occur during validation of the relevant rule (e.g. when saving):
```
KeyError: 'DictGroup(title=<title>,help_text=<help_text>)'
```