git-ecosystem / git-ecosystem/git-credential-manager
I have Ubuntu 22.04.4 LTS distro on my WSL2 (hosted on my Windows 11 23H2 x64 Pro).
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
I have Ubuntu 22.04.4 LTS distro on my WSL2 (hosted on my Windows 11 23H2 x64 Pro).
And I need to securely and persisently store credentials in non-interactive manner (without any user prompt).
Secret Service API definitelly require GUI, Git credential cache is not persistent, Plaintext files are not secure at all.
I've tried to use GPG/pass compatible files store. But if I set a passphrase for a generated GPG key a prompt starts to open in WSL2 terminal window (or in a GUI window if Seahorse is installed):
So GPG/pass compatible files don't require any interaction only if GPG key has no passphrase? No other options available on Linux?
Originally posted by @bairog in https://github.com/git-ecosystem/git-credential-manager/discussions/1680
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/credstores.md, especially the Secret Service API, Git credential cache, plaintext, and GPG/pass-compatible sections referenced in the report. Determine whether the requested non-interactive, persistent Linux/WSL credential storage requires documentation or a new implementation; done means the supported options and their security and prompt requirements are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, linux, ubuntu
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100