Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.6.9

Bug #21148 Throw bad-passphrase exception instead of key-not-found exception
Submitted: 2016-11-13 09:57 UTC
From: alec Assigned: alec
Status: Closed Package: Crypt_GPG (version 1.6.0b1)
PHP Version: Irrelevant OS:
Roadmaps: 1.6.0b2    
Comments Add Comment Add patch

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 45 + 41 = ?

 [2016-11-13 09:57 UTC] alec (Aleksander Machniak)
Description: ------------ Decrypting a message when: - it was encrypted with at least two keys - keyring contains only one private key - no addDecryptKey() was used before decrypt() throws Crypt_GPG_KeyNotFoundException instead of Crypt_GPG_BadPassphraseException. The lack of one private key does not cause inability to decrypt a message, so the user should be asked for passphrase.


 [2016-11-13 11:15 UTC] alec (Aleksander Machniak)
-Status: Open +Status: Closed -Assigned To: +Assigned To: alec
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.