Branch: refs/heads/2.3.0
Home:
https://github.com/Checkmk/checkmk
Commit: 1656565e8d5afb9ff211f0164817ec97f2d18c3e
https://github.com/Checkmk/checkmk/commit/1656565e8d5afb9ff211f0164817ec97f…
Author: Maximilian Wirtz <maximilian.wirtz(a)checkmk.com>
Date: 2024-02-15 (Thu, 15 Feb 2024)
Changed paths:
M Pipfile
M Pipfile.lock
Log Message:
-----------
Update cryptography
Change-Id: I31df5e4caef870c143877c8fd4e7e63c92bbf847
Commit: c2a0337bb6d369ffc7ddf3de5cf7d10312ebcaf1
https://github.com/Checkmk/checkmk/commit/c2a0337bb6d369ffc7ddf3de5cf7d1031…
Author: Hannes Rantzsch <hannes.rantzsch(a)checkmk.com>
Date: 2024-02-15 (Thu, 15 Feb 2024)
Changed paths:
M cmk/base/plugins/agent_based/checkmk_agent.py
M cmk/plugins/lib/checkmk.py
M cmk/utils/crypto/certificate.py
M tests/unit/cmk/utils/crypto/test_certificate.py
M tests/unit/cmk/utils/test_certs.py
Log Message:
-----------
Use timezone-aware datetimes in Certificate
Certificate.not_valid_before and not_valid_after now returns
timezone-aware datetimes (in UTC). This is possible thanks to
cryptography's new not_valid_before_utc function.
The expiry datetimes passed to Certificate during creation are also
expected to be timezone-aware now. If they are not, an assertion will
raise at runtime.
cryptography has also deprecated the old way of using naive datetimes,
so this should also get rid of the deprecation warnings.
Change-Id: Iaab87e0a8b60560050ce978c864bfa2da50de635
Commit: 88e7a7945f242e972ec392789c2bc55070510a06
https://github.com/Checkmk/checkmk/commit/88e7a7945f242e972ec392789c2bc5507…
Author: Maximilian Wirtz <maximilian.wirtz(a)checkmk.com>
Date: 2024-02-15 (Thu, 15 Feb 2024)
Changed paths:
M cmk/gui/watolib/config_domains.py
M tests/unit/cmk/gui/watolib/test_config_domains.py
Log Message:
-----------
Fix some CryptographyDeprecationWarning
Change-Id: I524524c54ff52f915c7fef327320476c2853f972
Compare:
https://github.com/Checkmk/checkmk/compare/abd2adb5a1be...88e7a7945f24