-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14.01.15 09:57, Werner Koch wrote:
> On Tue, 13 Jan 2015 21:33, dgouttegat...@incenp.org said:
>
>> [2] https://bugs.g10code.com/gnupg/issue1794
>
> Right, this is a blocker for a 2.1.2 release.
I have another strange appearance:
1. Generate a
On Tue, 13 Jan 2015 21:33, dgouttegat...@incenp.org said:
> [2] https://bugs.g10code.com/gnupg/issue1794
Right, this is a blocker for a 2.1.2 release.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
___
Gnup
On 01/13/2015 05:29 PM, Robert J. Hansen wrote:
... Now, maybe I'm missing something completely obvious here (and if so,
it wouldn't be the first time), but if I have the secret part of a
certificate, and that certificate is marked as ultimately trusted, isn't
it a bit odd that the user IDs would
Starting from an empty GnuPG 2.1.1 Win 7/x64 installation, I imported my
existing secret certificate for 0xD6B98E10 and set it to ultimate trust.
The result was a little ... weird.
C:\Users\rhansen>gpg --edit-key d6b98e10
Secret key is available.
pub dsa2048/D6B98E10
created: 2008-07-30
