Skip to content
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

Generate root strategy ncabatoff #7700

Merged
merged 6 commits into from
Oct 18, 2019

Conversation

ncabatoff
Copy link
Collaborator

No description provided.

vinodmu and others added 6 commits October 18, 2019 09:52
Shamir seals now come in two varieties: legacy and new-style. Legacy
Shamir is automatically converted to new-style when a rekey operation
is performed. All new Vault initializations using Shamir are new-style.

New-style Shamir writes an encrypted master key to storage, just like
AutoUnseal. The stored master key is encrypted using the shared key that
is split via Shamir's algorithm. Thus when unsealing, we take the key
fragments given, combine them into a Key-Encryption-Key, and use that
to decrypt the master key on disk. Then the master key is used to read
the keyring that decrypts the barrier.
# Conflicts:
#	vault/generate_root.go
@ncabatoff ncabatoff merged this pull request into generate-root-strategy Oct 18, 2019
vishalnayak pushed a commit that referenced this pull request Oct 18, 2019
* Adapt to new shamir-as-kek reality.
briankassouf pushed a commit that referenced this pull request Oct 23, 2019
)

* Abstract generate-root authentication into the strategy interface

* Generate root strategy ncabatoff (#7700)

* Adapt to new shamir-as-kek reality.

* Don't try to verify the master key when we might still be sealed (in
recovery mode).  Instead, verify it in the authenticate methods.
@ncabatoff ncabatoff deleted the generate-root-strategy-ncabatoff branch December 16, 2019 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants