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
