Problem encrypting to a hushmail gpg key

[Sean Rima]

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 it started, and my 
>>> key is a 1024 bit key and signs with SHA-1
>>> (to be fair, i imagine that whenever this becomes a 'real' threat, 
>>> hushmail will allow for modifications/new keys)
>>
>>> (2) the hushmail user probably will not be able to decrypt a gnupg 
>>> encrypted message in hushmail if the encryption algorithm chosen 
>>> isn't currently being used by hushmail, which, depending on how old 
>>> the key is, may not be the encryption algorithm listed on the key,
>>
>>> and if the hushmail user uses gnupg (preferable ;-) ), then he/she 
>>> would be better off generating a new key in gnupg, and just leave 
>>> the hushmail key for hushmail users
>>
>>
>> I will pass this info on, though how far we get is debatable :) Thanks
>> for the info
>>
> 
Ok, on this, I unstalled gpg 2.0.10 and installed 1.4.10b and I can
import and encrypt to Hushmail keys. Does this mean that gpg 2.0.10 is
broken or is it correctly handling the key where 1.4.10b is not

Sean
-- 
GSWoT and CaCert WOT Assurer
My public GPG Key http://sl.srima.eu/sfr
.tel  http://rima.tel/

I believe that every human has a finite number of
heartbeats. I don't intend to waste any of mine
running around doing exercises. - Neil Armstrong

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20100129/c5e74fd0/attachment-0001.pgp>