[Confusion] distinction between the 2 versions 1.4.6 & 2.0.3

[shirish]

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

Hi all,
      Lemme start at the clean slate with what has happened till now.
For exercises, understanding &  usage will be using the stable 2.0.3
release version in Ubuntu till I'm not clear in all the aspects.

gpg --armor --sign --encrypt -u 0x729A8B17  -r 0x729A8B17 myloveletter.txt

You need a passphrase to unlock the secret key for

 It works also with

gpg --a --s --e --u  0x729A8B17  -r 0x729A8B17 myloveletter.txt

 which resulted in a myloveletter.txt.asc file yippy!

 I was also able to decrypt it

ou need a passphrase to unlock the secret key for
user: "shirish some phrase here <shirishag75 at gmail.com>"
2048-bit ELG-E key, ID some id key here, created 2007-05-05 (main key
ID 729A8B17)

gpg: encrypted with 2048-bit ELG-E key, ID some id key here, created 2007-05-05
      "shirish some phrase here <shirishag75 at gmail.com>"
gpg: Signature made Friday 18 May 2007 12:29:23 AM IST using DSA key ID 729A8B17
gpg: Good signature from "shirish some phrase here <shirishag75 at gmail.com>"

ok the only thing I have changed in the decryption is

  ID key for ELG-E key as well as  some phrase here instead of the
actual phrase given.

All in all things seem good till this point.

 Now tomorrow will be trying with gpg2 , one thing though :-

Mr. Werner Koch had usefully provided the difference between 1.4.6 & 2.0.3

http://lists.gnupg.org/pipermail/gnupg-users/2007-May/031099.html

Now in that 1.4.6 had been shown as using ELG-E

while 2.0.3 as using ELG (I guess that's the final) hopefully
shouldn't spring surprises.

 I am sorry if I come out as paranoid but till I don't understand how
things work, I feel its best to be conservative.
- --
          Shirish Agarwal
  This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGTKrhlQ1T+3KaixcRAsASAJ9wnHc0Tng7kZabyL+FRZeCpd378QCdHpJk
SW/fIoqfaWrWcAPrg3NZvl8=
=3Bdr
-----END PGP SIGNATURE-----