Conversation
showi
approved these changes
Mar 29, 2024
5 tasks
Contributor
|
In my opinion, these lock mechanisms should rather be managed directly by the keychain, but I understand it is temporarily simpler like that, and easier to find and understand than |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When using the keychains, it's possible to run commands indefinitely unless you lock your keychain.
I'm adding a sub-mechanism to drop the key in keychain so it forces to re-ask for the master password on the next command.
For the ones more concerned about using the keychain: