docker / docker/docker-credential-helpers
pass: docker login does not work after rotating gpg key
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 195
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Description
Repro steps:
- Store a login cred:
aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin 123456789.dkr.ecr.us-east-1.amazonaws.com
- Rotate your gpg key
- Re-store the login cred with the same command as step 1
Expected result:
The creds are stored successfully
Actual result:
The old credentials can't be decrypted, so the credential helper fails with gpg: decryption failed: No secret key
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 by reproducing the issue with the AWS ECR docker login command shown in the report, then trace the credential helper's handling of an undecryptable stored credential after GPG key rotation. Done means re-storing credentials succeeds after rotation without the No secret key failure, with coverage for this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100