correct date when verify the signature
Hi all! What should i have to do if i want to see the correct date when i verify any signature? I have only one problem with it. For example: Every time when i verify any signature, i get the following date: gpg: Signature made 04/09/11 The first 2 digit of the year is always missing. What is the reason of it? Best regards, Csabi ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
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: gpg: encryption failed: public key not found
Sorry everyone because I should have made this clear on my first post: when I say I, I mean root. I log in that computer as sysadmin, so I do all my work there as root. That's why I don't understand what the problem is. There's only one keyring, containing root's keys and the recipient's public key (signed with root's key so it's trusted). The only thing I didn't think of is to mark it as trusted-key. I didn't think it was of any use since I thought that signing it with root's key would solve the trust issue, and anyway the problem is that gpg can't locate the key, but I can try it tomorrow at work just in case. Elena -- View this message in context: http://old.nabble.com/gpg%3A-encryption-failed%3A-public-key-not-found-tp31341625p31373082.html Sent from the GnuPG - User mailing list archive at Nabble.com. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: correct date when verify the signature
On Tue, 12 Apr 2011 08:47, db...@freemail.hu said: Every time when i verify any signature, i get the following date: gpg: Signature made 04/09/11 The first 2 digit of the year is always missing. What is the reason of it? That is definef by your locale. Run locale to see the settings for the current locale. You may run for example LC_ALL=C gpg . to use another locale for gpg. The function used to print the date is called asctimestamp and makes use of strftime where its format string is either the one returned nl_langinfo or lacking that fucntion the standard %c %Z. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Re: gpg: encryption failed: public key not found
123098 aoil...@hotmail.com writes: I log in that computer as sysadmin, so I do all my work there as root. OT, but you should be logging in as a normal user and using sudo instead. -- PGP: A0E4 B2D4 94E6 20EE 85BA E45B 63E4 2BD8 C58C 753A PGP: 2C23 EBFF DF1A 840D 2351 F5F5 F25B A03F 2152 36DA pgpemlE4myjJh.pgp Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
gpg 1.4.11 - problem with dyld when refreshing keys.
Hi, System: gpg 1.4.11 - Processor: PowerPC G4 (1.1) - MacOSX 10.5.8 Compiled from freshly downloaded source code: /.configure without flags Version info: gnupg 1.4.11 Configured for: Darwin (powerpc-apple-darwin9.8.0). Compiled and installed. When running from Terminal: $ gpg --refresh-keys Output starts with: gpg: requesting key C91B085E from http server subkeys.pgp.net dyld: Library not loaded: /usr/local/lib/libintl.3.dylib Referenced from: /usr/local/libexec/gnupg/gpgkeys_http Reason: image not found gpg: unnatural exit of external program gpg: no handler for keyserver scheme `http' Followed by 9 consecutive warnings application gpgkeys_http crashed (but the process continued). All those warnings had in common the following: Process: gpgkeys_http [1372] Path:/usr/local/libexec/gnupg/gpgkeys_http Identifier: gpgkeys_http Version: ??? (???) Code Type: PPC (Native) [...] Dyld Error Message: Library not loaded: /usr/local/lib/libintl.3.dylib Referenced from: /usr/local/libexec/gnupg/gpgkeys_http Reason: image not found The process continues, checking and reporting and concludes with: gpg: Total number processed: 37 gpg: unchanged: 30 gpg: new user IDs: 3 gpg: new signatures: 791 I have saved the complete outputs of gpg 1.4.11 compile, the 9 warnings, the --refresh-keys process. It they can be useful for further reference, I can e-mail them to whomever will ask. Thanks, Charly ___ 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
Re: gpg: encryption failed: public key not found
On 4/12/2011 3:03 AM, Jerome Baum wrote: 123098aoil...@hotmail.com writes: I log in that computer as sysadmin, so I do all my work there as root. OT Right, so, next time show some restraint. :) but you should be logging in as a normal user and using sudo instead. There is more than one way to do it. Just because using sudo may be the way that you are familiar with doesn't make it a one-size-fits-all solution. (And no, don't bother posting any elegant treatises on why sudo is the one true way. No point getting further off topic, and you won't convince me anyway.) Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpg: encryption failed: public key not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Doug Barton do...@dougbarton.us writes: On 4/12/2011 3:03 AM, Jerome Baum wrote: 123098aoil...@hotmail.com writes: I log in that computer as sysadmin, so I do all my work there as root. OT Right, so, next time show some restraint. :) Right. Since when was a little OT a problem? It's when things get out of hand and the signal-to-noise ratio gets messed up, that there's a problem. but you should be logging in as a normal user and using sudo instead. There is more than one way to do it. Just because using sudo may be the way that you are familiar with doesn't make it a one-size-fits-all solution. (And no, don't bother posting any elegant treatises on why sudo is the one true way. No point getting further off topic, and you won't convince me anyway.) I won't bother. logging in as a normal user and using sudo wasn't meant in the sudo is teh rulz sense. It was meant to stand more generally for don't 'casually' run destructive commands (think rm) and compile third-party software with more privileges than necessary -- whether you do that by logging in as another user and use sudo, or whether you implement this differently, doesn't really matter. What matters is that you lower your privileges to the minimum required and which can be practically applied. If you don't want to keep OT, happy to take this off-list and have an insightful discussion -- assuming it doesn't boil down to mis-communication per above. :) - -- PGP: A0E4 B2D4 94E6 20EE 85BA E45B 63E4 2BD8 C58C 753A PGP: 2C23 EBFF DF1A 840D 2351 F5F5 F25B A03F 2152 36DA -BEGIN PGP SIGNATURE- iQI+BAEBCgAoBQJNpJ/SIRhodHRwOi8vamVyb21lYmF1bS5jb20vamVyb21lLmFz YwAKCRBj5CvYxYx1OgCQEADHOYzw62gtCy7MVXHJqUoiRRxQ2OvLRez5gj1e/+xs aIcXAComJDMIcwyxtuBE8LRk2FK8ErjzHEneU7fNYXD9ahs/HmqEWv2eR7uNMzN/ a4R705Vqq7RtLKfV03N0ertPBaKdhlClgiyjO1O82dwF06UQYkXXnwK7e+t0fUR1 D0pOpBVQgVrhomSRjIEvkZfD1MbUI5TqsKeBYk6ELoFfGhIboS9JS1AMa7pVazpJ 4PyTtoXgjdiVIAXaZ+V6pzrdh+NdQhsx3yp7mLg/c7JJPnyzC8pDM2c28k0F9355 LNHEPm8ekl9sD2yP/QctOIx0EjlNMI6g8fyC9/wvqP6ZEYXkB8BdrpRuGfEfL8Cc M0ngk1OfFjw72OIpBXMV2kNuCIhVCfVqgWiftzcMW/YgIIIfMJ8APYaQZKzyJbGq +zYfWZxajkb3Vl+2imvlJCEius0rLsrxMbcXtXp6W6f/UFL8V0pGdlddhnYNrgeF UeFbIh64TAho7UvalLZtL23AVZmFCqXfX/TeaBWxAK5U/Qf14sQkHGbYQt/1LWYR MOcHAzcPFWUgttNKhE2azYOARfUVOq/a0dOEcf0fcBOkwra/3w1GXWOTvd72UoNU MWpL/0K6iUz6twnRtAOK1RjNkPaGge3nl+Er6bGfWBh4R4aKU7Im43K5NTTVtCE+ xA== =r87p -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
