Cipher v public key.

[Andreas Martin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Gray wrote:
>>> AES256 is listed as a cipher but not a public key?  What is the
>>> The difference?  I was hoping to use asymmetric keys with me 
>>> Giving the public key to the customer.  As mentioned before this all 
>>> Works fine but I'm not sure which alogorithm I'm using when encrypting. 
> 
>> You're using both an asymmetric key (RSA, DSA, ELG-E), and symmetric key
> (AES, CAST5, TWOFISH, etc) when you encrypt.
> 
> Sorry I may be missing the point but why does it now show AES or AES256 as a
> pukey? 

Do you mean "does it _now_ show" or "does it _not_ show"?

> Home: /SYS$LOGIN/gnupg
> Supported algorithms:
> Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA, ELG
> Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
> Hash: MD5, SHA1, RIPEMD160, SHA256
> Compression: Uncompressed, ZIP, ZLIB

AES is listed as a cipher, because ist is an algorithm for symmetric
encryption. It cannot be used as a public/secret-key algorithm (neither
now, nor in future).

Regards


Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iQCVAwUBRH1A5+f8mJnBT5ROAQLQ/gP+MHwyEcrN/SiMvw44GJEdimqCwseCYjpj
8Ir0us0IbBth9q0yVc/eiLExlm7Wwvog/6eB5P8qZ5bmpm3aUTcqZi5vFL7/2jF8
pf9AdBHOToG9lFIck+6La8xfs+lL1oN/gi4eCuAWytfM9i2EGS4NtZ0PMDNV/d/v
TwoPPIb21Do=
=UlPy
-----END PGP SIGNATURE-----