News for hackers. Stuff that matters.
Re:NeoPG – an opiniated fork of GnuPG 2 by jancsika on Wednesday January 17, 2018 @08:08PM (#16173741)
Should the NeoPG project mention why GPGME wasn't a suitable compromise?

I understand the author wants to clean up the core and the API, but if there's already a project that cleans up the API isn't that good enough? Especially considering the standard it implements-- PGP-- is still quite complicated.

Re:NeoPG – an opiniated fork of GnuPG 2 by aparadja on Thursday January 18, 2018 @01:41AM (#16175196)
Not exactly related to NeoPG, but GPGME in general: Doesn't GPGME assume that the user already has GnuPG 2.x installed and running on their system?

This might just be a misconception I have, but I always thought you couldn't make a batteries-included, self-contained, works-out-of-the-box app if you used GPGME. You'd first have to tell the user to go get a GnuPG implementation from somewhere.

I'd be super happy to be wrong on this.

Re:NeoPG – an opiniated fork of GnuPG 2 by lambdafu on Thursday January 18, 2018 @06:11AM (#16176218)
Yes, I should document that. GPGME only exposes a high-level API, and application developers often want more control. For example, you can't inspect key material before importing it, but importing a key is not a reversible operation - so applications sometimes use a temporary HOMEDIR for GPGME/GnuPG to import the key there and inspect it with a keylisting. It can be very cumbersome.
Re:NeoPG – an opiniated fork of GnuPG 2 by jopsen on Thursday January 18, 2018 @12:35AM (#16174935)
> Especially considering the standard it implements-- PGP-- is still quite complicated.

A standard without multiple independent implementations is a bit unhealthy..