feat: fix passphrase fatigue by wiring OS keychain caching into all CLI commands#112
Merged
feat: fix passphrase fatigue by wiring OS keychain caching into all CLI commands#112
Conversation
…LI commands The main `auths` binary used an in-process CachedPassphraseProvider that was empty on every invocation, prompting for a passphrase every time. Meanwhile `auths-sign` already used KeychainPassphraseProvider (OS keychain-backed, persists across invocations). - Replace CachedPassphraseProvider with KeychainPassphraseProvider in build_config() so all CLI commands benefit from OS keychain caching - Wire agent_signing into build_auths_context() so CommitSigningContext gets a real agent provider instead of NoopAgentProvider - Improve error messages for IncorrectPassphrase and PassphraseExhausted to surface AUTHS_PASSPHRASE and `auths agent start` options
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Auths Commit Verification
Result: ✅ 1/1 commits verified |
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
1 participant
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.
The main
authsbinary used an in-process CachedPassphraseProvider thatwas empty on every invocation, prompting for a passphrase every time.
Meanwhile
auths-signalready used KeychainPassphraseProvider (OSkeychain-backed, persists across invocations).
auths agent startoptions