On 4/25/2013 9:13 PM, Mason Loring Bliss wrote:
> I've been reading some "best practises" documents, and it was suggested that
> I not use SHA-1 as my self-signature digest algorithm:
Beware of "best practices." What makes a practice best depends greatly
on the specific threats you face, and unle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all.
I've been reading some "best practises" documents, and it was suggested that
I not use SHA-1 as my self-signature digest algorithm:
https://we.riseup.net/debian/openpgp-best-practices#self-signatures-must-not-use-sha1
This says, "To fix th
On Thu, Apr 25, 2013 at 5:17 PM, sansay wrote:
> Hi all,
>
> I am completely stumped.
> I can't change the passphrase on a gpg key. Here is the whole interaction:
>
> bash-4.1$ gpg --edit-key 8267977F
> gpg (GnuPG) 2.0.14; Copyright (C) 2009 Free Software Foundation, Inc.
> This is free software:
sansay gmail.com> writes:
>
> Hi all,
>
> I am completely stumped.
> I can't change the passphrase on a gpg key. Here is the whole interaction:
>
> bash-4.1$ gpg --edit-key 8267977F
> gpg (GnuPG) 2.0.14; Copyright (C) 2009 Free Software Foundation, Inc.
> This is free software: you are free to
Hi all,
I am completely stumped.
I can't change the passphrase on a gpg key. Here is the whole interaction:
bash-4.1$ gpg --edit-key 8267977F
gpg (GnuPG) 2.0.14; Copyright (C) 2009 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRAN
On Thu, 25 Apr 2013 01:11, jhar...@widomaker.com said:
> I don't see a .sig, so do these hashes (SHA1, SHA256) look correct?
It is now there.
>
> 4dafebee7b0c7adde2b27473faca7236851cf472
> 72af477e33b15baf6733af3e5e5c49c18ddf398b8a90e93c65d04cb34f04f00b
> 4277493 ./alpha/gnupg/gnupg-2.0.20
On Wed, 24 Apr 2013 23:04, da...@systemoverlord.com said:
> * Decryption using smartcards keys > 3072 bit does not work.
s/not/now/
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
___
Gnupg-users mailing lis
