Am Montag, 31. August 2015, 11:13:42 schrieb Andre Heinecke: > Hi, > > On Sunday, August 30, 2015 08:04:59 PM Rolf Eike Beer wrote: > > Jeremy Whiting wrote: > > > On Sun, Aug 30, 2015 at 8:48 AM, Jeremy Whiting <[email protected]> wrote: > > > > Hey all, > > > > > > > > I may have found another candidate for unmaintained. KGpg is a ui for > > > > gnupg. I've never used it, but have used kleopatra. Anyway, here's my > > > > reasoning. Please fix any false assumptions I may have made if you > > > > know kgpg or kleopatra better than I: > > > > > > > > 1. KGpg does gnupg. Kleopatra also does, but is maintained. > > > > 2. KGpg has not been ported to Qt5/kf5, Kleopatra has. > > > > 3. KGpg isn't part of kdepim nor is it maintained by the PIM team, > > > > Kleopatra is. > > > > > > > > Is there anything that KGpg does that Kleopatra doesn't/can't do? Or > > > > is there any reason to port KGpg to Qt5/kf5 and keep releasing it? > > > > > > Correction, KGpg is maintained, Rolf made commits as late as last > > > month. My mistake. I gave KGpg a try here and it does seem to work > > > well. Rolf, could you use a hand porting it to Qt5/KF5 ? > > > > I did not port for the reason that KGpg depends on kdepimlibs (KABC), > > which > > had no Qt5-based release yet (now it has), and I must confess I can occupy > > my time with other stuff and was too lazy to build it from git. In fact I > > was asked at least twice why there was no KF5-port and both were also too > > lazy to build kdepimlibs stuff themself. Now that there is a release it > > makes actually sense to port, so I hope I can manage it in time for 15.12. > > If someone is bored and wants to assist I will not reject any efforts. > > What's the state of GnuPG 2.1 support in KGpg? I've tried to run KGpg (from > debian jessie) on my with 2.1 and it fails to start with an error that It > can't find the Gpg-agent. (Probably because there is no mandatory > GPG_AGENT_INFO anymore)
https://bugs.kde.org/show_bug.cgi?id=340676 I.e. that one should be fixed since 14.12, but other issues exist. > > Kleopatra can do X.509, which KGpg can't. I never found that really > > missing. > So you probably never much had encrypted communiction with instutional > users. ;-) S/MIME is pretty widespread there. (At least in Germany) > > > And KGpg looks so much more beautiful ;) > > Aww, now you've hurt Kleopatra's feelings (Doesn't she have a cute nose) ;-) > > But I have to agree there at least for the keylisting. (as Sune and Anne > also wrote in the other branch of this topich). The Keylisting / > visualization of validity is imho better in Kgpg. Something I hope to > address in Kleopatra at some point. This will probably go along with > GnuPG's TOFU database / usage statistics that are currently worked at. > Which will also need new > representation in GUI's. > > Kleopatra at least has the advantage that it uses the official API (gpgme) > and so it is theoratically much easier to work with new features and > different versions of GnuPG. Yes, sort of. OTOH one does not need that additional library installed if KGpg should be used. > I'd much rather see us working together on a single GUI then splitting the > effort to work on two Certificate Managers in the KDE community. Of course I > doub't that will happen. > If you are willing to work on KGpg Ok! Alternatives are good. :-) This discussion came up years ago already. At the end I think we agreed to disagree. Or something like that. > There is also another advantage KGpg has over kleopatra, The Kleopatra > codebase is kind of a beast with a usage of stdc++ and boost that is > probably unfamiliar to most KDE hackers. > > > And it has the CAFF mode, which I doubt Kleopatra has. > > I actually did not know that. Maybe something we could add to Kleopatra > then, too. It's important that https://bugs.kde.org/show_bug.cgi?id=332368 get's fixed before. Currently KGpg can send such mails, but not with KMail/Kontact. I removed kde-community from CC, they don't want that I post there. Greetings, Eike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
