gt; CC: ved...@nym.hush.com; gnupg-users@gnupg.org
> Subject: Re: "SHA1 Protection" from way to see what cipher/algo was used to
> create your key?
>
> On 21/06/12 15:00, Sam Smith wrote:
> > when running the command: gpg --list-packets
> >
> > there is an
On 06/21/2012 09:57 AM, Peter Lebbing wrote:
> There is no cipher
> or hashing involved in creating a key...
This may or may not be true, depending on what method of random number
generation is being used. ANSI X9.17, Yarrow and Fortuna are three
examples of pseudorandom number generators that ar
On Jun 21, 2012, at 9:00 AM, Sam Smith wrote:
> when running the command: gpg --list-packets
>
> there is an outputted line that reads: "SHA1 protection"
>
> I did some looking online and saw that this line stays even when people
> change their hash algorithm to something else (like SHA2).
>
On 21/06/12 15:00, Sam Smith wrote:
> when running the command: gpg --list-packets
>
> there is an outputted line that reads: "SHA1 protection"
First of all, it seems you understand it, but let me emphasize this: the
algorithms you get when using the inspection method vedaal showed you, are /no
when running the command: gpg --list-packets
there is an outputted line that reads: "SHA1 protection"
I did some looking online and saw that this line stays even when people change
their hash algorithm to something else (like SHA2).
If the "SHA1 protection" is not indicating the use of SHA1
