Hi Thomas!
On Fri, 23 Jun 2000, Thomas 'Balu' Walter wrote:
> Hiho...
> I just installed 1.2.2, read the README.UPGRADE and sourced gpg.rc
> into my muttrc.
>
> Being a GPG-newbie I am wondering why it asks me to choose a key from
> the following list now:
>
> 1 + 1024/0xBFB1428C DSA -s Thomas Walter (Balu) <[EMAIL PROTECTED]>
> 2 + 1024/0xE9AAF668 ElG e- Thomas Walter (Balu) <[EMAIL PROTECTED]>
> 3 + 1024/0xBFB1428C DSA -s Thomas Walter (Balu) <[EMAIL PROTECTED]>
> 4 + 1024/0xE9AAF668 ElG e- Thomas Walter (Balu) <[EMAIL PROTECTED]>
>
> And no matter which I choose I get (if I want to encrypt a message):
>
> gpg: using secondary key E9AAF668 instead of primary key BFB1428C
> gpg: This key belongs to us
> gpg: reading from `/tmp/mutt-MS1-24207-4'
> gpg: writing to `-'
> gpg: ELG-E/BLOWFISH encrypted for: E9AAF668 Thomas Walter (Balu) <[EMAIL PROTECTED]>
If you look at the list, there are really only two keys:
0xBFB1428C is a signing key (-s)
0xE9AAF668 is an encryption key (e-)
Both are repeated, giving the illusion of four keys. You cannot
encrypt using a signing key, so gpg uses the encrypting key :)
The choice is given because when you encrypt a message, it must be
encrypted using the _recipient's_ key. The gpg output you see is
telling you:
a) I have to use the encrypting key instead
b) It's our key, so we're encrypting to ourselves
c) the input and output files (which are a mutt temp file and stdout)
d) a message telling you that it _did_ encrypt it to the person
specified
--
_
_|_|_
( ) * Anton Graham
/v\ / <[EMAIL PROTECTED]>
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
