The page https://help.riseup.net/en/security/message-security/openpgp/best-practices#self-signatures-must-not-use-sha1
explains how to check for deprecated md5 or sha1 signatures:
self-signatures must not use SHA1
You can check this by doing
On Sat, 28 Jun 2014 15:22, ds...@jabberwocky.com said:
> I put a limited workaround in GnuPG at the time - that's why the
> encryption key is always written to the card after the auth key (so
> the encryption key would always be the "newest". Of course, that
I have noch checked by I assume that
On Jun 29, 2014, at 6:23 AM, Werner Koch wrote:
> On Sat, 28 Jun 2014 15:22, ds...@jabberwocky.com said:
>
>> I put a limited workaround in GnuPG at the time - that's why the
>> encryption key is always written to the card after the auth key (so
>> the encryption key would always be the "newest"
On Sat, 28 Jun 2014 22:47, vmaa...@gmail.com said:
> I'm using the FSFE card [1] with SCR3500 [2]. Ok yeah sure, that’s a
> fellowship card but I actually also wanted to point out the SCR3500
Right. Some friends told me that this works really well for them. BTW,
the fellowship card is exactly th
Hello Gnupg-users,
i used gpg4win 2.0.20 gpa 0.9.4 to create a key pair for one of my email accnts.
only it says under tech details, "this key has only a public part".
i tested an email, it was encrypted but i can't decrypt it. i thought it would
auto create the key pairs pub/priv ?
can i fi