Support for storing recovery key in keychain. #127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apologies for the chonker here. Summary of changes below
There are several configuration options for the keychain in the keychain mostly around ACLs for the item and whether or not it will appear in Keychain.app
CommonNameForEscrow
it will use the native go http lib with a TLS transport config from the keychain. Otherwise it will continue to use curl.GenerateNewKey
can be set with a profile now. It will track the rotation in a separate preference which can be removed to make multiple generations.