Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Stefan Kamphausen <skampi@gmx.de>
Subject: Re: More Encryption Woes: MML/PGP uses my own key
Date: Mon, 07 Feb 2005 08:39:53 +0100	[thread overview]
Message-ID: <85zmyg4y46.fsf@mail.bn-software.de> (raw)
In-Reply-To: <ilud5vfmesb.fsf@latte.josefsson.org>

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.


      reply	other threads:[~2005-02-07  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 10:02 Stefan Kamphausen
2005-02-05 11:23 ` Simon Josefsson
2005-02-07  7:39   ` Stefan Kamphausen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85zmyg4y46.fsf@mail.bn-software.de \
    --to=skampi@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).