More Encryption Woes: MML/PGP uses my own key

More Encryption Woes: MML/PGP uses my own key

[Stefan Kamphausen]

Dear Gnus-Community,

first: I hope I'm not being embarassing with all my questions these
days.  Please tell me, if so.

After having tested all the SMIME stuff yesterday (thanks for the
answers, I'll try to make use of them) I went into the GPG encryption
today.  I tested it by encrypting with my ID at the office to my
private ID.  Obviously they both have the same name and only differ in
the email address.

Now using C-c C-c c o inserts an mml-tag of the form
   <#secure method=pgp mode=signencrypt>
into the message.  When I then send it, it get's encrypted with my
public key from my _office ID_ so that I can decrypt it here at this
place.  Inserting another field into the mml-tag:
   recipient="Stefan Kamphausen <my@privateemail.de>" 
didnt help either.  

I didn't check whether I can decrypt it with my private ID because I
don't have that secret key here.  I only mention this because the
output buffer of mml contains some hints that that message might be
encrypted using _both_ keys. (see output below)

As always: any hints or pointers to documentation appreciated.

Regards
Stefan

PS: The (slightly modified) *MML2015 Result* buffer (only masked my
email adresses to keep them spam free)

[GNUPG:] ENC_TO 86430035F5BBAAC7 16 0
[GNUPG:] ENC_TO 0DEE63CD458C2FDE 16 0
[GNUPG:] USERID_HINT 0DEE63CD458C2FDE Stefan Kamphausen <me@myofficeplace.de>
[GNUPG:] NEED_PASSPHRASE 0DEE63CD458C2FDE 030B87D16C9E6D21 16 0
[GNUPG:] GOOD_PASSPHRASE
gpg: encrypted with 1024-bit ELG-E key, ID F5BBAAC7, created 2003-02-16
      "Stefan Kamphausen <my@privateemail.de>"
[GNUPG:] NO_SECKEY 86430035F5BBAAC7
gpg: encrypted with 2048-bit ELG-E key, ID 458C2FDE, created 2004-07-13
      "Stefan Kamphausen <me@myofficeplace>"
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] PLAINTEXT 62 1106905550 
[GNUPG:] PLAINTEXT_LENGTH 283
gpg: Signature made Fri Jan 28 10:45:50 2005 CET using DSA key ID 6C9E6D21
[GNUPG:] SIG_ID TsN6bG7qDXSmC02z5LIEmO0zCYY 2005-01-28 1106905550
[GNUPG:] GOODSIG 030B87D16C9E6D21 Stefan Kamphausen <me@myofficeplace.de>
gpg: Good signature from "Stefan Kamphausen <me@myofficeplace.de>"
[GNUPG:] VALIDSIG 697DA91F3A3E257A1E7FF5E4030B87D16C9E6D21 2005-01-28 1106905550 0 3 0 17 2 00 697DA91F3A3E257A1E7FF5E4030B87D16C9E6D21
[GNUPG:] TRUST_ULTIMATE
[GNUPG:] DECRYPTION_OKAY
[GNUPG:] GOODMDC
[GNUPG:] END_DECRYPTION

-- 
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.

Re: More Encryption Woes: MML/PGP uses my own key

[Simon Josefsson]

Stefan Kamphausen <skampi@gmx.de> writes:

> Dear Gnus-Community,
>
> first: I hope I'm not being embarassing with all my questions these
> days.  Please tell me, if so.
>
> After having tested all the SMIME stuff yesterday (thanks for the
> answers, I'll try to make use of them) I went into the GPG encryption
> today.  I tested it by encrypting with my ID at the office to my
> private ID.  Obviously they both have the same name and only differ in
> the email address.
>
> Now using C-c C-c c o inserts an mml-tag of the form
>    <#secure method=pgp mode=signencrypt>
> into the message.  When I then send it, it get's encrypted with my
> public key from my _office ID_ so that I can decrypt it here at this
> place.  Inserting another field into the mml-tag:
>    recipient="Stefan Kamphausen <my@privateemail.de>" 
> didnt help either.  

Maybe sender="Stefan Kamphausen <my@privateemail.de>" is what you
meant?

You could also add a default-key keyword to .gnupg/gpg.conf, to let it
pick the correct key, I have:

default-key B565716F

Re: More Encryption Woes: MML/PGP uses my own key

[Stefan Kamphausen]

Hi,

Simon Josefsson <jas@extundo.com> writes:

> Stefan Kamphausen <skampi@gmx.de> writes:
>
>> Dear Gnus-Community,
>>
>> first: I hope I'm not being embarassing with all my questions these
>> days.  Please tell me, if so.
>>
>> After having tested all the SMIME stuff yesterday (thanks for the
>> answers, I'll try to make use of them) I went into the GPG encryption
>> today.  I tested it by encrypting with my ID at the office to my
>> private ID.  Obviously they both have the same name and only differ in
>> the email address.
>>
>> Now using C-c C-c c o inserts an mml-tag of the form
>>    <#secure method=pgp mode=signencrypt>
>> into the message.  When I then send it, it get's encrypted with my
>> public key from my _office ID_ so that I can decrypt it here at this
>> place.  Inserting another field into the mml-tag:
>>    recipient="Stefan Kamphausen <my@privateemail.de>" 
>> didnt help either.  
>
> Maybe sender="Stefan Kamphausen <my@privateemail.de>" is what you
> meant?

Sorry if I've been fuzzy in my problem description.

I am sitting at the office and want to send an encrypted email to my
private account for which I have the public key at hand.

Now encrypting and sending in any way leads to a message that seems to
contain the encrypted message for _both_ the recipient (my private
address) and the sender (my at the office).  

Of course it is useful if the message that was Gcc'ed is encrypted
with my office-key so that I can actually access my outbox but I
really wonder why the outgoing message is encrypted with both keys. 

> You could also add a default-key keyword to .gnupg/gpg.conf, to let it
> pick the correct key, I have:
>
> default-key B565716F

I didn't know about that, that might come in handy in other
situations.  Thanks.

Regards
Stefan
-- 
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.