Summary: | net-misc/keychain-2.8 fails to recognize GPG keys | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | zlg (RETIRED) <zlg> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | drobbins, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
zlg (RETIRED)
2015-04-25 11:02:27 UTC
Daniel, what is your app-crypt/gnupg version? I've got 2.1.3-r2. And the problem is this that both keychain and gnupg get minor upgrade at once: keychain: 2.7.x -> 2.8.x and gnupg: 2.0.x -> 2.1.x. Currently using app-crypt/gnupg-2.1.3-r3 (merged 2015-04-22). Try adding the --agents ssh,gpg option. Keychain now defaults to only starting ssh-agent. (In reply to Daniel Robbins from comment #3) > Try adding the --agents ssh,gpg option. Keychain now defaults to only > starting ssh-agent. Odd; I had tried that prior, but I believe it was `--agents gpg,ssh`, and after the key arguments. Does position matter in this case? I tried that flag between `/usr/bin/keychain` and the args/keys and it worked AOK. I'll mark the bug accordingly. Thanks for the clarification! For anyone stumbling across this in the future: /usr/bin/keychain --agents ssh,gpg ${SSHKEY} ${GPGKEY} Worked. |