On Thu, 28 Jan 2016 20:15, r...@sixdemonbag.org said:
> Really? I thought GPGME had a dependency on libgpg-error, and the
> COPYING file for that is clearly GPLv2.
That is just a file. COPYING describes the licence used for the manual
and the tools. COPYING.LIB describes the license for the li
> That is right for GnuPG but not for GPGME. From gpgme/AUTHORS:
Really? I thought GPGME had a dependency on libgpg-error, and the
COPYING file for that is clearly GPLv2.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailma
On 1/28/2016 4:32 AM, Robert J. Hansen wrote:
...
>
> Antony Prince was the guy updating Guardian Project's code. See the
> thread at:
>
> http://www.gossamer-threads.com/lists/gnupg/users/73146
>
> According to Antony, you can grab his updates from:
>
> ftp://blazrsoft.com/gnupg-f
On Thu, 28 Jan 2016 11:54, r...@sixdemonbag.org said:
> The GnuPG developers have historically been unwilling to provide GPGME
> under any terms except the GPL. If you need an LGPLed GPGME, you're out
> of luck.
That is right for GnuPG but not for GPGME. From gpgme/AUTHORS:
License (software)
> Moreover the license is GPL and we would need LGPG. Maybe this point
> could be solved with separate license negotiations.
The GnuPG developers have historically been unwilling to provide GPGME
under any terms except the GPL. If you need an LGPLed GPGME, you're out
of luck.
If you can't/won't
> Thank you for this encouraging words. In fact I got solved another problem.
Woot!
> The only problem remaining is that the application still ignores my
> own password callback and uses the GnuPG default:
This is actually expected behavior. See:
https://bugs.gnupg.org/gnupg/issue767
On Tue 2016-01-26 06:02:09 -0500, Sandra Schreiner wrote:
[ Robert J. Hansen wrote: ]
>> Are you getting periodic messages about "Not enough random bytes
>> available. Please do some other work to give the OS a chance to
>> collect more entropy! (Need 167 more bytes)" or something like that?
>
>
