Bug 1696602
Summary: | systemd-cryptsetup: Serialize access to memory hard enabled keyslots while unlocking many LUKS devices | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Ondrej Kozina <okozina> |
Component: | systemd | Assignee: | Michal Sekletar <msekleta> |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.1 | CC: | fsumsal, jstodola, msekleta, systemd-maint-list |
Target Milestone: | rc | ||
Target Release: | 8.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | systemd-239-20.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:44:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1668138 | ||
Bug Blocks: | 1776036 |
Description
Ondrej Kozina
2019-04-05 08:39:33 UTC
(The flag that turns the serialization on is CRYPT_ACTIVATE_SERIALIZE_MEMORY_HARD_PBKDF. It's accepted by any crypt_activate_by_* function from libcryptsetup API) Upstream PR, https://github.com/systemd/systemd/pull/14168 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1794 |