-
Notifications
You must be signed in to change notification settings - Fork 4.4k
disable_mlock must now be explicitly included in config #29974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
disable_mlock must now be explicitly included in config #29974
Conversation
5818a2b
to
084be9c
Compare
CI Results: |
e977c8f
to
7aececf
Compare
command/server.go
Outdated
entCheckRequestLimiter(c, config) | ||
|
||
if config != nil { |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
7aececf
to
c44c565
Compare
71b840e
to
8780c7a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we wanted this to be mandatory only if using integrated storage?
Build Results: |
@sgmiller I took another look at the requirements and you're right. I'll switch this back to draft on continue working on it. |
…sablemlock-config
…sablemlock-config
…sablemlock-config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Use active voice. Co-authored-by: Sarah Chavis <[email protected]>
10626a9
…sablemlock-config
…sablemlock-config
…sablemlock-config
…sablemlock-config
…sablemlock-config
Synchronize the `enos` directory on 1.19 with that of `main` after changes introduced in #29974 were not backported. Signed-off-by: Ryan Cragun <[email protected]>
Synchronize the `enos` directory on 1.19 with that of `main` after changes introduced in #29974 were not backported. Signed-off-by: Ryan Cragun <[email protected]>
Description
This PR eliminates a default value for
disable_mlock
for integrated storage.disable_mlock
must now be set explicitly in a configuration file or env var if using integrated storage.When Vault starts up with mlock enabled, Vault with integrated storage is prone to running out of memory because it doesn't allow the use of swap disk. However, while disabling mlock helps not run into OOM problems, it is a security issue because allowing for swapping to disk means that secret values can be viewed in plaintext if the swap files are inspected.
As such, Vault will no longer initialize until this value has been explicitly configured, and we will provide a clear explanation in the error message of the tradeoffs of choosing to enable or disable mlock on Integrated Storage.
We must also update documentation to include the new behavior.
TODO only if you're a HashiCorp employee
backport/
label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x
, but older release branches will bebackport/ent/x.x.x+ent
.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.