Problem with C++ wrapper and gpgme

[Yenot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 26 May 2003 11:29 pm, David Shaw wrote:
>
> Do you mean "--export" here?  --list-keys just lists keys, and does
> not include much information you might want (key flags, etc).

I meant "--export".  Thanks David.


On Monday 26 May 2003 10:40 pm, Robert J. Hansen wrote:
>
> Unfortunately, the raw binary format is undocumented, near as I can
> see.

The format of OpenPGP data is well documented in RFC2440. It can be
difficult to understand/parse OpenPGP data, because of backwards
compatibility with multiple versions of the standard. All the same,
it's manageable.


On Monday 26 May 2003 10:14 pm, Marcus Brinkmann wrote:
>
> The one thing that can save you even if you use GPGME is that GPGME
> can be used asynchronously, ie you can use the partial results
> returned by GPGME to start to display the keylist.

This can be done with the raw "gpg --export" output as well.  In the
raw format, GnuPG returns even thousands of keys almost
instantaneously.  If your parsing code isn't fast enough, you can
start the display of keys in chunks.

>
> You can often trade performance against generality.  This is ok as
> long as you know what you are doing, and are aware of the
> consequences.

I don't think anyone wants to parse the raw OpenPGP data.  I posted
what I think is the only way to solve the current bottleneck. GnuPG
needs a good keymanager. If it was as simple as writing a GUI on an
existing backend, Linux would already have multiple GUI keymanagers
that are superior (or at least as good as) the commercial PGP GUI. As
it stands, existing keymanagers are intolerably slow with large
keyrings and they can't manipulate and/or display all key features.

 - Yenot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+0n4mP247TY29IxARAgPJAJ9f5yswjtHX8OxDrbXnl9Kp59DnMQCgiWu4
75MMBOkDpjb1OHADTjd92yc=
=a9xD
-----END PGP SIGNATURE-----