Hello Bill !
Bill House bhouse1...@gmail.com wrote:
The showpref on the key does not mention IDEA, which leaves me also
with no idea how IDEA is in the mix.
Cipher: AES256, AES192, AES, CAST5, 3DES
Digest: SHA256, SHA1, SHA384, SHA512, SHA224
Compression: ZLIB, BZIP2, ZIP,
The initial install had written a gpg.conf file that seems to have
been the problem. I replaced it with a new gpg.conf that has the
default-key set to the new keyid I made and the problem is solved.
Thanks to all for the help!
Bill House
___
Surely this is a newbie question, but I have been trying for some time to
get GPG to create a signed and encrypted file. Not wanting to go through
the whole recompile thing and not caring to use the IDEA cipher, it seems to
me that GPG should simply work by default. Sadly, it does not seem to
On Apr 13, 2010, at 4:06 PM, Bill House wrote:
Surely this is a newbie question, but I have been trying for some time to get
GPG to create a signed and encrypted file. Not wanting to go through the
whole recompile thing and not caring to use the IDEA cipher, it seems to me
that GPG should
On 4/13/2010 4:06 PM, Bill House wrote:
I created a new RSA/RSA 2048 key in my keyring. So long as I only want
to encrypt, it works fine. When I want to encrypt AND sign, it
complains that I need the IDEA algorithm. When I specify the
cipher-algo, it either claims the cipher is invalid,
The showpref on the key does not mention IDEA, which leaves me also
with no idea how IDEA is in the mix.
Cipher: AES256, AES192, AES, CAST5, 3DES
Digest: SHA256, SHA1, SHA384, SHA512, SHA224
Compression: ZLIB, BZIP2, ZIP, Uncompressed
Features: MDC, Keyserver no-modify
Bill
