[pkg-gnupg-maint] Bug#638619: Bug#638619: Misleading "gpg: Ohhhh jeeee: no decrypt() for 17" message from gpg when trying to decrypt a file without the public key being imported

[NIIBE Yutaka]

On 05/08/2015 02:58 PM, NIIBE Yutaka wrote:
> Please let us know reproducible scenario if it still exists in current
> gpg 1.4.  If it is not reproducible, I wonder if we can close this bug?

Finally, I managed to reproduce this bug.  Here is my scenario.

(1) With --gen-key, generate DSA+Elgamal key
(2) make a encrypted file using (1)
(3) make a copy of .gnupg/secring.gpg
(4) With --edit-key, delkey Elgamal subkey
(5) With --export, make public key file
(6) With --delete-secret-key, delete the key generated by (1)
(7) Restore .gnupg/secring.gpg by the copy of (3)
(8) Import DSA only public key of (5)

Now, it has secret subkey, but no corresponding public key.

(8) Try to decrypt encrypted file of (2)
    It asks the passphrase, then input it, then, it stops with:

	gpg: Ohhhh jeeee: no decrypt() for 17

GnuPG is 1.4.18-7 in stable.  I think that it is better to
check availability of public key for the subkey.
--