Looking for Elgamal sign+encrypt key information

[Atom 'Smasher']

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

> > in that case, what would be a good way (or ways) to force the sender to
> > use the RSA encryption key, and only use the ElGamal encryption key if RSA
> > isn't supported on their end?
>
> The RFC applies to implementations, not use models.
========================

it would be within the scope of an RFC to specify how an application might
handle encryption key preferences. it does, after all, specify how to
handle cipher preferences.


	...atom

 _________________________________________
 PGP key - http://atom.smasher.org/pgp.txt
 3EBE 2810 30AE 601D 54B2 4A90 9C28 0BBF 3D7D 41E3
 -------------------------------------------------

	"There is a theory which states that if ever anyone discovers
	 exactly what the Universe is for and why it is here, it will
	 instantly disappear and be replaced by something even more
	 bizarrely inexplicable. There is another theory which states
	 that this has already happened."
		-- Douglas Adams
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures

iD8DBQFAVompnCgLvz19QeMRAi5lAKCTNHOnvZ74YwuBkCdRyQZT0ftTtwCdHswy
4pVei9TbyDtPZyygkWa1nGU=
=6INn
-----END PGP SIGNATURE-----