On 10/02/2016 12:10 AM, Arbiel (gmx) wrote:
In fact, I wish to record "secrets" in gnome-keyrings, as seahorse does,
and I am looking for tutorials which explain how to do so with bash
scripts, which are the only "programs" I am able to write.
Then you might have a look at the secret-tool progr
https://lists.gnupg.org/pipermail/gnupg-users/2016-October/056809.html
> Frankly, I did not know how to translate the German term
> "Schnappschloss". I had in mind that a "latch" is similar to a
> "deadbolt".
Heinz Diehl wrote:
> Visualising a picture of what is meant by the German term, I would
On Sun, 02 Oct 2016 12:44:16 +0200
"Julian H. Stacey" wrote:
>https://lists.gnupg.org/pipermail/gnupg-users/2016-October/056809.html
>> Frankly, I did not know how to translate the German term
>> "Schnappschloss". I had in mind that a "latch" is similar to a
>> "deadbolt".
>
>Heinz Diehl wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I had to do two things to solve this:
1: use absolute paths for the homedir. E.g.:
gpg --homedir "C:\users\me\test\gpg" --gen-key
2: kill any existing GnuPG agents with task manager, and then start one
manually using the same homedir:
gpg
First a quote from the gpg 2.1.15 man page:
--trust-model pgp|classic|tofu|tofu+pgp|direct|always|auto
[...]
In the TOFU model, policies are associated with bindings
between keys and email addresses (which are extracted from
user ids and normalized
Dear All,
I'd tried to play around with the (new) Python bindings announced just
a few days ago, but I am a bit lost. I am using Python-2.7 on MacOS
"El Captain", with Python-2.7, gpg2, gpgme (1.6.0_2) and the bindings
py27-pygpgme and pyme all installed using MacPorts.
(Yes, that is not t
