Summary: | app-crypt/gnupg-2.0.10: USE="-smartcard" not honored by gpg-agent's ssh support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Boney McCracker <brendlerjg> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | c1pher |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Boney McCracker
2009-02-21 09:01:30 UTC
perhaps a strace of some failing processes and comparing them to a working processes may indicate a cause. Careful not to disclose a private key too. I was completely unable to replicate this with gnupg-2.0.15 . gnupg-2.0.10 is no longer even in the tree. Should this perhaps get closed? I have no objection. I gave up trying to use it for ssh. Disregard my previous comment. I opened my mouth a little to soon and now I get to insert my foot into it. I will see if I can figure out why this is going on and report back. Sorry for the confusion. Ok. I think I have all my facts straight now. First thing: error getting default authentication keyID of card: Not supported shows up in my logs regardless of whether I have gpg-agent in a working state or a broken state. I don't believe this was the actual root of the problem. I did, however, have to deviate from the original circumstances in order to make everything play nice. I changed what was your .bashrc to: if [ -f "${HOME}/.gpg-agent-info" ]; then . "${HOME}/.gpg-agent-info" export GPG_AGENT_INFO export SSH_AUTH_SOCK export SSH_AGENT_PID fi I also moved what was originally in .xsession to .kde4/Autostart/01-gpg-agent. Doesn't change anything. Just makes it play nice with kdm etc. Worth noting, it is possible your original problem had to do with not being able to find pinentry or some other older known bug. It also would have been in the logs, just under or just over the smartcard one and would have looked like: can't connect to the PIN entry module: IPC connect call failed End result: I still think this can safely be closed. The current gpg-agent in the tree seems to work fine and the error being produced, although it shows up, appears to be expected and doesn't affect it working. Thanks for your help. I'll have to give it another try some time. Please feel free to close it. Going ahead and closing. |