[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] gpgmepp missing key edit api
From:       Stefan Gehn <mETz81 () web ! de>
Date:       2006-06-03 0:20:53
Message-ID: 200606030220.53545.mETz81 () web ! de
[Download RAW message or body]

Am Samstag, 3. Juni 2006 01:24 schrieb Ingo Klöcker:
> On Friday 02 June 2006 20:36, Stefan Gehn wrote:
> > Any ideas? Is key editing planned for gpgmepp? It's called "minor
> > missing feature" in the README which doesn't sound like anybody cares
> > about it.
>
> It seems key editing wasn't needed for the Ägypten project. Therefore it
> hasn't been implemented yet.

Probably because the primary goal was S/MIME support. Unfortunately S/MIME is 
not really suitable for cheap or decentralized security, although it's way 
more comfortable if you happen to have certificates for everybody.

> Since gpgmepp is just a C++ wrapper for 
> gpgme, gpgmepp should be extended to support anything gpgme supports.
> Unfortunately, I can't help with 2 at the moment.
>

Ok, no problem.

After some more reading I have found Kleo::GnuPGProcessBase and I think I will 
use that as a way to implement signing. When gpgmepp supports key signing we 
can still switch the job over.

Btw, will libkleopatra and gpgmepp both end up in kdepimlibs (I hope so)? 
Maybe it would be even better to move gpgmepp out of kde (kdesupport?) so 
others have a chance of using it.

Bye, 
Stefan aka mETz
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]