On Tue, 5 May 2015 01:14, l...@greenhost.nl said:
> keypair we would also like to generate a revocation certificate. Keys
> are passwordless, so at first I thought that it should be straight forward.
Note that GnuPG 2.1 generates revocation certificates by default.
> for the revocation certific
On Mon, 4 May 2015 17:58, diaf...@gmail.com said:
> Gotcha. Would it be possible to throw an error when --with-sig-check
> is included with --import or --recv-keys? When silently ignored, it is
> very easy for a user to assume that the signature checks passed.
No. The purporse of the --with-* op
luis wrote:
> To: gnupg-users
> Subject: generating revocation certs non-interactively
>
ECHO Y\n0\n\nY\n|GPG --command-fd 0 --gen-revoke 0xDEADBEEF
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-us
On 05/04/2015 03:05 PM, te...@elde.net wrote:
> Hi list,
>
> I've got what seems to be a not too uncommon setup, with a primary key used
> only
> for certifying, then separate signature, encryption and authentication keys as
> subkeys. I wanted to make new ones, and have the subkeys on a Yubikey
On 05/05/15 09:41, Werner Koch wrote:
> Note that GnuPG 2.1 generates revocation certificates by default.
Great! Good to know!
> The idea is that you should be able to tell the reason for the
> revocation.
Yes of course, this makes perfect sense. There is however the fact that
good practice gui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> This made me notice that my --card-status does the same thing, it
> shows my signing subkey at "General key info" (although I thought
> at some point it used to show the master...). That said, everything
> works fine and my card is usable (v2.1.3).
*SOLVED*
On Tue, Apr 28, 2015 at 11:12 AM, Dan Bryant wrote:
> OK... I'm apparently suffering from a bad gpgsm setup. According to
> the 2011 post
> (https://lists.gnupg.org/pipermail/gnupg-devel/2011-March/025989.html)
> the following command, should just work:
>gpgsm --gen-key | gpgsm --i
