fix(keychain): configure macOS credential access - #531
Merged
Conversation
majd
force-pushed
the
bugfix/keychain_item_label
branch
from
August 29, 2026 13:11
62f111d to
eb55834
Compare
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
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.
Summary
Compatibility
The Keychain service, account key, serialized credential payload, and backend order are unchanged. Existing authenticated users continue reading the same item, and existing ACLs are preserved because duplicate-item updates do not replace access control.
The trust setting applies only when creating a new macOS item. It trusts only the creating executable, not all applications. A different bundled path or signing identity may still prompt once and require Always Allow.
Validation
Closes #517