[Confusion] distinction between the 2 versions 1.4.6 & 2.0.3

Thu May 17 06:24:34 CEST 2007

> Message: 6
> Date: Wed, 16 May 2007 23:04:27 +0530
> From: shirish <shirishag75 at gmail.com>
> Subject: Re: [Confusion] distinction between the 2 versions 1.4.6 &
>         2.0.3
> To: gnupg-users at gnupg.org
> Cc: groups at caseyljones.net
> Message-ID:
>         <511f47f50705161034k62c18753u7907277212a7dd7b at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hi all,
>
> > Message: 7
> > Date: Tue, 15 May 2007 22:18:45 -0700
> > From: Casey Jones <groups at caseyljones.net>
> > Subject: Re: [Confusion] distinction between the 2 versions 1.4.6 &
> >         2.0.3   &       how to make the key compliant with 2.0.3
> > To: gnupg-users at gnupg.org
> > Message-ID: <464A9435.6080808 at caseyljones.net>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >
> > shirish wrote:
> >
> > >  Also what do u guys think of Mr. Casey Jones, do u think he's right
> > > at the above.
> >
> > Werner posted that the keys should be identical between the versions, so
> > I guess my suggestion shouldn't be necessary. Therefore I withdraw my
> > suggestion. It still might be worth a try though. Just make sure your
> > backups are good before you mess with your key.
> >
> > Before you do that though, try signing and encrypting a file with gpg
> > from the command line and checking to see that it will validate. That
> > way you'll know if the problem is gpg or firepg.
> >
> > First, to verify that you have your keys in an accessible place and to
> > remind you what your key ID is:
> > gpg --list-keys
> >
> > Then sign and encrypt to an ascii file using your own key ID when it
> > asks for recipient:
> > gpg -a -se yourloveletter.txt
>
>  Casey could you give me more precise instructions please. How do I
> sign & encrypt to an ascii file using my key ID (public key ID perhaps? )
>
> https://help.ubuntu.com/community/GnuPrivacyGuardHowto
>
> Let's take the e.g. there :-
>
> gpg: key D8FC66D2 marked as ultimately trusted
> public and secret key created and signed.
>
> pub   1024D/D8FC66D2 2005-09-08
>       Key fingerprint = 95BD 8377 2644 DD4F 28B5  2C37 0F6E 4CA6 D8FC 66D2
> uid                  Dennis Kaarsemaker (Tutorial key) <dennis at kaarsemaker.net>
> sub   2048g/389AA63E 2005-09-08
>
> > Then see if it works:
> > gpg --decrypt yourloveletter.txt.asc
> >
> > I like to use the -a when testing like this just so it will come out in
> > an ascii format that I can enjoy looking at instead of the default
> > binary format.
>  ------------------------------
>
>  Please lemme know how to proceed further. We can also take this
> off-list if you feel to be more appropriate. I don't know how the list
> would look at this.
> --
>           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
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 16 May 2007 13:00:44 -0500
> From: John Clizbe <JPClizbe at tx.rr.com>
> Subject: Re: [Confusion] distinction between the 2 versions 1.4.6 &
>         2.0.3
> To: GnuPG Users <gnupg-users at gnupg.org>
> Message-ID: <464B46CC.9070605 at tx.rr.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> shirish wrote:
>
> >> Then sign and encrypt to an ascii file using your own key ID when it
> >> asks for recipient:
> >> gpg -a -se yourloveletter.txt
> >
> >  Casey could you give me more precise instructions please. How do I
> > sign & encrypt to an ascii file using my key ID (public key ID perhaps? )
> >
> >
> > gpg: key D8FC66D2 marked as ultimately trusted
> > public and secret key created and signed.
>
> gpg -a -se -u 0xD8FC66D2 -r 0xD8FC66D2 yourloveletter.txt
>
> -u specifies the signing key (same as --local-user)
> -r specifies the recipient's key, ie the key to encrypt to
>
> gpg will ask for your key's passphrase in order to sign the message.
>
> -u does not need specified if you have set a default-key in gpg.conf.
> If default-key is not set and -u is not specified, gpg will use the first key
> found in the secret keyring.
>
> >> Then see if it works:
> >> gpg --decrypt yourloveletter.txt.asc
>
> gpg will ask for your key's passphrase in order to decrypt the message.
>
>
>
> --
> John P. Clizbe                      Inet:   John (a) Mozilla-Enigmail.org
> You can't spell fiasco without SCO. PGP/GPG KeyID: 0x608D2A10/0x18BB373A
> "what's the key to success?"        / "two words: good decisions."
> "what's the key to good decisions?" /  "one word: experience."
> "how do i get experience?"          / "two words: bad decisions."
>
> "Just how do the residents of Haiku, Hawai'i hold conversations?"
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 662 bytes
> Desc: OpenPGP digital signature
> Url : /pipermail/attachments/20070516/0684d671/attachment-0001.pgp

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

Hi John,
        First of all thank you for your help . I tried with my key id
all the combinations

gpg -a -se -u 0xD8FC66D2 -r 0xD8FC66D2 yourloveletter.txt

but I get
gpg: Invalid option "-a-se-u"

. I tried both ways using zero (0xkeyid) as well as using alphabet O
(oxkeyid)  but either way I get the same error

 gpg: Invalid option "-a-se-u"

I also  tried with space between gpg and the flags -a-se-u as well as
without space

gpg -a-se-u (0 or Oxkeyid) as well as gpg-a-se-u which told me the
former is the one to be used.

Then finally hit a brainwave and did

gpg -a -se -u OxD8FC66D2 -r OxD8FC66D2 myloveletter.txt

 With space between each flag

gpg: skipped "OxD8FC66D2": secret key not available
gpg: myloveletter.txt: sign+encrypt failed: secret key not available

Then I get this error. Can anybody explain me what's going wrong here?
 I have substituted my keyid with the general keyid. Don't know if its safe to
give out my keyid or not?

Looking for answers. Thank you all for your time.
- --
          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

iD8DBQFGS9kHlQ1T+3KaixcRAuLBAKCNg5XnShCZyrB7XqGvGKRqzQg6UgCeNl62
g4YUxHsw5GcyYhDVYPgnTyc=
=LbiK
-----END PGP SIGNATURE-----