Problem with migration from 1.2.4 to 2.0.9
Im having problems migrating from version 1.2.4 to 2.0.9 I have transfered all my keys from the old envirmoment to the new enviroment. Now our applications can't use the api in the software to decrypt a file anymore. The passphrase does not work any more. If I want to remove the passprase I get this error: You need a passphrase to unlock the secret key for user: ... 2048-bit RSA key, ID 182D0209, created 2011-03-30 can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory gpg-agent[22946]: command get_passphrase failed: Operation cancelled gpg: cancelled by user Can't edit this key: General error How can I fix this? ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problem with migration from 1.2.4 to 2.0.9
On 14:59, Michel Mansens wrote: Im having problems migrating from version 1.2.4 to 2.0.9 I have transfered all my keys from the old envirmoment to the new enviroment. Now our applications can't use the api in the software to decrypt a file anymore. The passphrase does not work any more. If I want to remove the passprase I get this error: You need a passphrase to unlock the secret key for user: ... 2048-bit RSA key, ID 182D0209, created 2011-03-30 can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory gpg-agent[22946]: command get_passphrase failed: Operation cancelled gpg: cancelled by user Can't edit this key: General error How can I fix this? this might be related to some changes they made in the keys a while back I think PGP V6 used one key for both signing and encrypting but if you look at the keys now you see each key has a sub-key as well one used for signing and the other for encryption. so i don't see how you can bring the old style key forward if i'm right about the change I just junked the keyring from PGP658WIN ( the old MIT version ) . actually I kinda like the idea of using separate encryption and signing keys, but too: we should all consider how we will implement our policy on expiration dates. when my key expires I will generate a new one and upload it to the keyserver. hopefully the keyserver will be smart enough to understand that I need to supersede my key and not give mu a bunch of 'duplicate record' crap. if it gives any trouble in this regard oh well: it just ain't ready for use yet. -- /WM -- /MIKE signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problem with migration from 1.2.4 to 2.0.9
Michel Mansens wrote the following on 4/12/11 3:31 AM: can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory gpg-agent[22946]: command get_passphrase failed: Operation cancelled gpg: cancelled by user Can't edit this key: General error How can I fix this? I tried to find out from the raw source of your e-mail what platform you are running. But as it often happens with @gmail.com addresses, this kind of information is not displayed. The current stable gpg2 is 2.0.17. How did you install 2.0.9? 2.0.9 uses gpg-agent to cache the passphrase, and pinentry to enter the passphrase. can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory is typical of gpg-agent not being activated. I'm a Macintosh user, and I don't know enough about your problem to help you really. If you would post to the list more information about what OS you are running (and its version), how you installed 2.0.9, and the output to the following commands after the prompt in Terminal: gpg-agent cat ~/.gpg-agent-info I hope that more knowledgeable list members will be able to help. Charly MacOS 10.6.7-MacBook Intel C2Duo 2GHz-GnuPG 1.4.11-MacGPG 2.0.17 Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 Enigmail 1.2a1pre (20110408-1936) ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problem with migration from 1.2.4 to 2.0.9
On 14:59, Michel Mansens wrote: Im having problems migrating from version 1.2.4 to 2.0.9 I have transfered all my keys from the old envirmoment to the new enviroment. Now our applications can't use the api in the software to decrypt a file anymore. The passphrase does not work any more. If I want to remove the passprase I get this error: You need a passphrase to unlock the secret key for user: ... 2048-bit RSA key, ID 182D0209, created 2011-03-30 can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory gpg-agent[22946]: command get_passphrase failed: Operation cancelled gpg: cancelled by user Can't edit this key: General error How can I fix this? this might be related to some changes they made in the keys a while back I think PGP V6 used one key for both signing and encrypting but if you look at the keys now you see each key has a sub-key as well one used for signing and the other for encryption. so i don't see how you can bring the old style key forward if i'm right about the change I just junked the keyring from PGP658WIN ( the old MIT version ) . actually I kinda like the idea of using separate encryption and signing keys, but too: we should all consider how we will implement our policy on expiration dates. when my key expires I will generate a new one and upload it to the keyserver. hopefully the keyserver will be smart enough to understand that I need to supersede my key and not give mu a bunch of 'duplicate record' crap. if it gives any trouble in this regard oh well: it just ain't ready for use yet. -- /WM signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problem with migration from 1.2.4 to 2.0.9
Hi, Im running Linux Redhat. The current version come with the installation of the OS. cat ~/.gpg-agent-info GPG_AGENT_INFO=/tmp/gpg-uCD8LF/S.gpg-agent:31303:1 SSH_AUTH_SOCK=/tmp/gpg-uaSl2w/S.gpg-agent.ssh SSH_AGENT_PID=31303 But is seems we have now problems with the agent process. We could decrypt data when I imported the key but now not at all. And when I tried to run the socket (agent) process we crashed the complete server and we had to hard shut-down it. Is it not possible to not use the agent? We also now trying to create a key on our production server and also this giving problems. It hangs when you have to type random letters after the password prompt. Thanks. 2011/4/12 Charly Avital shavi...@mac.com Michel Mansens wrote the following on 4/12/11 3:31 AM: can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory gpg-agent[22946]: command get_passphrase failed: Operation cancelled gpg: cancelled by user Can't edit this key: General error How can I fix this? I tried to find out from the raw source of your e-mail what platform you are running. But as it often happens with @gmail.com addresses, this kind of information is not displayed. The current stable gpg2 is 2.0.17. How did you install 2.0.9? 2.0.9 uses gpg-agent to cache the passphrase, and pinentry to enter the passphrase. can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory is typical of gpg-agent not being activated. I'm a Macintosh user, and I don't know enough about your problem to help you really. If you would post to the list more information about what OS you are running (and its version), how you installed 2.0.9, and the output to the following commands after the prompt in Terminal: gpg-agent cat ~/.gpg-agent-info I hope that more knowledgeable list members will be able to help. Charly MacOS 10.6.7-MacBook Intel C2Duo 2GHz-GnuPG 1.4.11-MacGPG 2.0.17 Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 Enigmail 1.2a1pre (20110408-1936) ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
