Am Mittwoch 22 März 2017 18:15:36 schrieb Werner Koch:
> On Fri, 17 Mar 2017 10:56, bernhard.rei...@intevation.de said:
> > As the command line is not a stable API to GnuPG, there were changes and
> > there will be changes to the command line over several versions. It maybe
> > in the
>
> That is n
Am Dienstag 14 März 2017 11:39:12 schrieb Michael J Gruber:
> >> The problem is the "difficult" upgrade path and mixed installations with
> >> gpg and gpg2.1+ that some distributions force upon you:
> >>
> >> As soon as you start gpg2.1, your (secret) key store is migrated to a
> >> new format with
Am Montag 13 März 2017 11:14:57 schrieb Michael J Gruber:
> Ævar Arnfjörð Bjarmason venit, vidit, dixit 10.03.2017 15:23:
> > On Fri, Mar 10, 2017 at 11:00 AM, Bernhard E. Reiter
> >> please consider using libgpgme interfacing to GnuPG, because the gpg
> >> co
Am Samstag 11 März 2017 01:10:31 schrieb brian m. carlson:
> On Fri, Mar 10, 2017 at 11:00:07AM +0100, Bernhard E. Reiter wrote:
> > but even better would be to move to libgpgme. >:)
>
> There are a couple potential problems I see with this approach. First,
> I'd
Am Freitag 10 März 2017 19:54:19 schrieb Linus Torvalds:
> On Fri, Mar 10, 2017 at 2:00 AM, Bernhard E. Reiter
> > please consider using libgpgme interfacing to GnuPG, because the gpg
> > command-line interface is not considered an official API to GnuPG by the
> > GnuPG-devs
Dear Git-Devs,
git uses an pipe-and-exec approach to running a GnuPG binary
as writen in the documentation [1]:
gpg.program
Use this custom program instead of "gpg" found on $PATH when making
or verifying a PGP signature. The program must support the same
com
6 matches
Mail list logo
