David
Yes the key is generated by hushmail.com. Not sure if they will listen
to me, but I will forward this to the list where the problem
originated
Thanks for the help and sorry for top posting, on my BlackBerry (and
sadly no gnupg)
Sean
On 1/29/10, David Shaw wrote:
> On Jan 17, 2010, at 12:
On Jan 17, 2010, at 12:23 PM, Sean Rima wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi
>
> A friend on the pgpnet mailing list is using a hushmail.com gpg key but
> when I import it, I get:
>
> C:\Users\Sean Rima>gpg --import < test.txt
> gpg: key C4E23A82: accepted non self-si
On 29/01/2010 16:31, Sean Rima wrote:
{think I sent my last wrong}
>>
>>> it is not a great idea to use hushmail keys for open pgp encryption
>>> or authentication
>>
>>> (1) the keys are not updated, and can't be for the same email
>>> address,
>>> so, for example, i've been with hushmail since
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 26/01/2010 18:52, ved...@hush.com wrote:
> Sean Rima it is not a great idea to use hushmail keys for open pgp encryption
> or authentication
>
> (1) the keys are not updated, and can't be for the same email
> address,
> so, for example, i'v
Sean Rima A friend on the pgpnet mailing list is using a hushmail.com gpg
key >but when I import it, I get
>gpg: key C4E23A82: public key ""-...@hushmail.com"
"
>imported
>gpg: Total number processed: 1
>gpg: imported: 1 (RSA: 1)
...
:public sub key packet:
version 4, al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
A friend on the pgpnet mailing list is using a hushmail.com gpg key but
when I import it, I get:
C:\Users\Sean Rima>gpg --import < test.txt
gpg: key C4E23A82: accepted non self-signed user ID
""**...@hushmail.com" <-...@hushmail.com>"
gpg: key