jaraco / jaraco/keyring

No recommended backend was available.

Open
#568 12 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

macOS
Dominant language
Python
Stars
1.5k
Forks
196
PR merge metrics
No merged PRs in 30d

Description

+1
happens for me on my mac with M1. It seems he doesn't find the backend, but it exists.
The fix was to use pip install keyrings.alt so it installs an alternative backend, but I can't see the entered password on the keychain, it seems independent from the system keychain, which is annoying.

Originally posted by @PyMarc2 in https://github.com/jaraco/keyring/issues/566#issuecomment-1087915367

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the missing-backend behavior on a Mac with an M1 processor, then compare the normal backend with the keyrings.alt workaround. The issue does not name files or tests; done would mean the intended backend is discovered and credentials use the system keychain rather than an independent store.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, python
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.