Proposal for a Desktop Neutral Crypto API

[Nate Nielsen]

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

Marc Mutz wrote:
> What's wrong with gpgme, then?
> 
> It's encryption system neutral, desktop neutral, mt-safe, provides both sync 
> and async interfaces (including integration into GTK and Qt event loops), is 
> there for years, has turned 1.0 last year, is used in KMail, mutt, Sylpheed, 
> Kleopatra, KAddressBook, and probably lots of other MUAs.
> 
> I've based gpgme++, qgpgme and libkleopatra onto it's API, so naturally, I 
> don't want to see us wasting effort and bandwidth on something that already 
> exists.

Nothing is wrong with GPGME. Seahorse uses it extensively. In fact most
implementors of this API would use GPGME. This API one level above
GPGME, at the user interface and high level object level, and allow us
to do things (ease of use, ui consintency, etc...) that are difficult at
a low level.

Cheers,
Nate

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

iD8DBQFCVOlpe/sRCNknZa8RApPFAKDfSfoLd9gds4SjxH5SxQw/F2I+8gCeLh0j
hl71xmVNpQG58uNUtslBl2A=
=763L
-----END PGP SIGNATURE-----