Re: [PGPNET] Jerome
On Mar 31, 2011, at 1:25 PM, gnupg-users-requ...@gnupg.org wrote: ... Pretty simple: Receiving messages with GPG 2.0.14 (Ubuntu Maverick, via Mint Linux): When messages to multiple recipients have the key ID's thrown, gpg-agent (?) sequentially requests passwords for all secret key many, many, many times, but fails to decrypt with any key---even the correct one. -- Thanks! Lance W. Haverkamp All, I can confirm the exact same problem when running under Mac 10.6.7. -- Scott Blystone Rochester, New York Gossamer Spider WoT Introducer (see http://www.gswot.org) Start SSL Notary (see http://www.startssl.com) CA Cert Assurer (see http://www.cacert.org) ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: [PGPNET] Jerome
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 MFPA expires2...@ymail.com writes: Are you implying something? Also, while I can't try this myself (using gpg1), would be good if someone would file a bug report. And maybe discus it on GnuPG-Users... Good point. CC'ing them so we can continue the discussion there. To summarize: gpg-agent seems to have problems handling thrown keyids. - -- 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- Version: GnuPG v1.4.9 (Cygwin) iQI+BAEBCgAoBQJNjgtfIRhodHRwOi8vamVyb21lYmF1bS5jb20vamVyb21lLmFz YwAKCRBj5CvYxYx1OsjCD/9NYbClVfgvasu4Tp4wdgiHbLMVX7Xvzksx77iNtUea z1w9ADSqbmQCsfFRd1QdWJb2qDtuEof4W9EbQJpu+ZFdOGSnvrbmpLUub2GYTmcx LAliISVCc5vmQWooO0BmBaOZUv7I+in8neSu9G1sh0+EGKLulDgNvRmZjpyaliAS qdg10KLjkfEIv1WQCk+1DA1yPvM5Yug3w5XrMa33tUZ6FWd2bR8NkcX+S1M1w75g x49cSmEIbnJMMGVWgjL1Vhsn10SMd3r4C5skL/l1svvL/HbdoHl01NWuoesi3wn/ 5YwjyKIY7PZoqs0DdgWlki2C7bJNXa2dWvlZZmRmcpW/5OgAtbtrAeda698RPQ/m qWB5O+V9QTNPVAQWQk9kahYu/ANjtRwbLDxEYaCfyWGiignoIsii7dMdpaCmFT8Z OauZ16LhRnXMe54XG5/jTa8f/lreNON3J5amJWH/hTp07FL8j7HxxLiHPY0aldgh obdOuFcjeOefuhjdL5V7PvsNrBYoT8+zDyV7PVkXyJb7/B6f9qA0rNAJ3x5xLtKZ DttiYopZ0AIk594m36qtKvg6vV/1m9xEY4VelI7Z6AQS3h73w+hLjSuXl4rNGS3b gb89GcB1Ub5QiBGpyvKZObm0op+Od8tqLfkSYbtMRRDYI56+YtvnU9EAbBFJVFJm Nw== =pR1O -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: [PGPNET] Jerome
On Sat, 26 Mar 2011 16:50, jer...@jeromebaum.com said: summarize: gpg-agent seems to have problems handling thrown keyids. You mean the current development version? Quite possible; that is for what development versions are for. For 2.0.x there can't be a problem because gpg-agent does not know anything about keyids because it is only used as a passphrase caching agent. 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: [PGPNET] Jerome
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Werner Koch w...@gnupg.org writes: On Sat, 26 Mar 2011 16:50, jer...@jeromebaum.com said: summarize: gpg-agent seems to have problems handling thrown keyids. You mean the current development version? Quite possible; that is for what development versions are for. I don't know which version -- some guys in PGPNET are reporting this. For 2.0.x there can't be a problem because gpg-agent does not know anything about keyids because it is only used as a passphrase caching agent. Again, I don't know anything about this. As you can see in my original email (the part where I quoted myself), I use gpg1. - -- 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- Version: GnuPG v1.4.9 (Cygwin) iQI+BAEBCgAoBQJNjiEZIRhodHRwOi8vamVyb21lYmF1bS5jb20vamVyb21lLmFz YwAKCRBj5CvYxYx1Ok6ND/9WUe92J60gGbTvTj7wWBAeQ59wCgnrOaN316v3XYZT YxVCkZFaocFVlU8PAEaeqr+RU2I6W5i4Abu7GQIlJrC+HC4vrb/rSWpbD/58v7jq Vzom51/BTUBVznbXR+USQxoxbezcQrtTUHHAH+qRp2oWfK+JYOO6MmPaIzuRAKU1 cnhgw7pdGj7vVeNuypbwF1x/X+fXRN48jKb+DxdbmMW/aQ+4JEU9exKRPOh3p3Pw OelQjGC0wYHLFjCvKFLn4nQ5CTJUEeDTx/A2vpyXmIUmuw3nVJWju4IGyOkAq2Im +yThWWx5BdWAl802e7Z4mtAAWs5tApuQhilOdgnInzSp+1QRmZQcm2Jth0wnGYKX gDwpnLf+ljMZv8z0bYR3fpZ+K6EaLGpRcNl3QaNNz/zpc6opJWqiWimGj9fLwc1D wKNJZGJ3cKLotVCXDr3ZkKBVuHq9+b1KT6Zloon30oPVlhrIfZ21NYPgAkxntvI5 ZReTmZ7jZuxxc2fx0mCNK+dsPxb7BRxbYkkIXGVpQtVz83Dv6XaZrVTEdfp06FZj IcOC3/vIzOKzLa6VKvQED+F5cBk9eSEmIzwY9nnHUgITa+ERvxPPdu04PnSsjzNP 3SKiIYg4IXPcQhSEknAtv+9OkUfMUQNgRhFmFuJv/G9rzuPWtZSeO4K5K79o0IOC Xw== =YT4l -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: [PGPNET] Jerome
On 03/26/2011 11:23 AM, Jerome Baum wrote: Werner Koch w...@gnupg.org writes: On Sat, 26 Mar 2011 16:50, jer...@jeromebaum.com said: summarize: gpg-agent seems to have problems handling thrown keyids. You mean the current development version? Quite possible; that is for what development versions are for. I don't know which version -- some guys in PGPNET are reporting this. For 2.0.x there can't be a problem because gpg-agent does not know anything about keyids because it is only used as a passphrase caching agent. Again, I don't know anything about this. As you can see in my original email (the part where I quoted myself), I use gpg1. Pretty simple: Receiving messages with GPG 2.0.14 (Ubuntu Maverick, via Mint Linux): When messages to multiple recipients have the key ID's thrown, gpg-agent (?) sequentially requests passwords for all secret key many, many, many times, but fails to decrypt with any key---even the correct one. -- Thanks! Lance W. Haverkamp 719-357-5745 (office) la...@thehaverkamps.net Contact encryption info: http://thehaverkamps.net/?Lance:Contact_Me http://facebook.com/LanceHaverkamp ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: [PGPNET] Jerome
On 03/26/2011 02:16 PM, Lance W. Haverkamp wrote: On 03/26/2011 11:23 AM, Jerome Baum wrote: Werner Koch w...@gnupg.org writes: On Sat, 26 Mar 2011 16:50, jer...@jeromebaum.com said: summarize: gpg-agent seems to have problems handling thrown keyids. You mean the current development version? Quite possible; that is for what development versions are for. I don't know which version -- some guys in PGPNET are reporting this. For 2.0.x there can't be a problem because gpg-agent does not know anything about keyids because it is only used as a passphrase caching agent. Again, I don't know anything about this. As you can see in my original email (the part where I quoted myself), I use gpg1. Pretty simple: Receiving messages with GPG 2.0.14 (Ubuntu Maverick, via Mint Linux): When messages to multiple recipients have the key ID's thrown, gpg-agent (?) sequentially requests passwords for all secret key many, many, many times, but fails to decrypt with any key---even the correct one. Can you create an easy reproducible? Does something like this exhibit the same broken behavior on your system? grant@johnyaya:~$ echo foo | gpg2 --throw-keyids -r k...@grant-olson.net -r la...@thehaverkamps.net --encrypt --armor | gpg2 --decrypt - gpg: using character set `utf-8' gpg: armor: BEGIN PGP MESSAGE Version: GnuPG v2.0.18-git1226772 (GNU/Linux) :pubkey enc packet: version 3, algo 16, keyid data: [4095 bits] data: [4096 bits] gpg: armor header: gpg: public key is :pubkey enc packet: version 3, algo 1, keyid data: [2048 bits] gpg: public key is gpg: anonymous recipient; trying secret key 6A8F7CF6 ... gpg: okay, we are the anonymous recipient. gpg: public key encrypted data: good DEK :encrypted data packet: length: 63 mdc_method: 2 gpg: encrypted with ELG key, ID gpg: encrypted with RSA key, ID gpg: AES256 encrypted data :compressed packet: algo=2 :literal data packet: mode b (62), created 1301168561, name=, raw data: 4 bytes gpg: original file name='' foo gpg: decryption okay -- -Grant Look around! Can you construct some sort of rudimentary lathe? signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
