Daiki Ueno

"-&N" is a special filename which gpg and GPGME (C library) use to denote a file descriptor. see --enable-special-filenames option of gpg: https://www.gnupg.org/documentation/manuals/gnupg/GPG-Esoteric-Options.html#index-enable_002dspecial_002dfilenames however, I can't reproduce it with gpg...

Indeed, the relevant function `gpgme_data_set_file_name` is not exported from the ruby interface. A PR adding it would be appreciated.

Oh indeed, my working copy was outdated. So if you have 2.0.16 installed you should be able to set it with `GPGME::Data#file_name=`.

If you are still able to reproduce it, can you try the debugging steps described at: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=blob;f=doc/gpgme.texi;h=e32657406d3f857184ba7d3172a42d7e9672e66a;hb=HEAD#l6050 (unfortunately, HTML version is not up to date)

well, the error can happen in various ways. shall we stop the guess work and try the standard diagnostics: ``` $ GPGME_DEBUG=9 irb ~ irb(main):001:0> require 'gpgme' GPGME 2014-06-06 14:00:21...

glad that we've finally got the log. I think GPGME (the C library) should report a better error message in that case, though your GnuPG version is way too old....

I have no idea, but this looks obviously wrong, unless you build it with ```--use-system-libraries```: ``` checking for gpgme_op_export_keys()... no ``` Could you collect the complete logs with ```--disable-clean```? ```...

well, though you seem to have use cases, I'm still not convinced that the new method will improve usability. actually: `find(:public, "")` is written shorter than: `find_exact(:public, "[email protected]")` could you...

OK, that makes sense. However, I feel the method itself a bit too specific. I'd suggest: - extend find method to accept matching style like `find(:public, "[email protected]", :match => :email)`...

oops, I thought I've added a guard for that but it was not enough. fixed: https://github.com/ueno/ruby-gpgme/commit/ae4eae90fbba84dac80b3f69fd7891f8cf8f105c