Gnus development mailing list
 help / color / mirror / Atom feed
From: Nathan Sullivan <alfonso@pants.nu>
Subject: Re: Encrypting outgoing message but not Gcc?
Date: Sun, 07 Dec 2003 03:07:03 -0800	[thread overview]
Message-ID: <87zne43mzs.fsf@shampoo.pants.nu> (raw)
In-Reply-To: <87r7zh8k9h.fsf@virgil.koldfront.dk> ( =?iso-8859-1?q?Adam_Sj=F8gren's_message_of?= "Sun, 07 Dec 2003 02:54:50 +0100")

spamtrap@koldfront.dk (Adam Sjøgren) writes:

> On Sat, 06 Dec 2003 13:35:21 -0500, Lloyd wrote:
>
>> Also, I think there's a gap somewhere in my understanding of all
>> this.  How can it be that something encrypted twice, once with the
>> recipient's public key and once with yours, would only need your
>> private key to be decrypted?  Wouldn't there have to be two
>> decryptions, one for each of the previous encryptions?  Or in this
>> case, is the encryption done with some sort of mathematical
>> combination of both public keys, such that either corresponding
>> private key can decrypt it?
>
> I'm not able to adequately and comprehensibly explain the theory, but
> I think it's a proporty of either assymetric key cryptography in
> general or the way PGP/GnuPG is constructed (the latter being less
> likely, probably, perhaps).

It's a property of the way almost all assymetric cryptography is
implemented.  The problem is that public key encryption is grotesquely
slow, so programs like PGP/GPG don't encrypt the entire message with
the public key.  Instead, they encrypt the message with a symmetric
cypher, like IDEA or Blowfish, then encrypt the symmetric key with the
public key for the desired recipient.  If you have multiple
recipients, then multiple copies of the encrypted symmetric key are
included, each encrypted for a specific public key pair.

-- 
	    Nathan Sullivan                     alfonso@pants.nu
-------------------------------------------------------------------------------
          Conscience is what hurts when everthing else feels so good.



  parent reply	other threads:[~2003-12-07 11:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06 16:17 Lloyd Zusman
2003-12-06 16:46 ` Adam Sjøgren
2003-12-06 18:35   ` Lloyd Zusman
2003-12-07  1:54     ` Adam Sjøgren
2003-12-07  2:09       ` Lloyd Zusman
2003-12-07  2:25         ` Adam Sjøgren
2003-12-07  2:37           ` Lloyd Zusman
2003-12-07 11:07       ` Nathan Sullivan [this message]
2003-12-07 11:35         ` Adam Sjøgren
2003-12-07 13:08         ` Lloyd Zusman
2003-12-06 17:24 ` Reiner Steib
2003-12-06 17:58   ` Lloyd Zusman
2003-12-07 13:35   ` Lloyd Zusman
2003-12-07 13:45   ` Lloyd Zusman
2003-12-07 15:16     ` Lloyd Zusman
2003-12-07 15:44       ` Simon Josefsson
2003-12-07 16:28         ` Lloyd Zusman
2003-12-06 17:47 ` Simon Josefsson
2003-12-07 16:50   ` Lloyd Zusman

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=87zne43mzs.fsf@shampoo.pants.nu \
    --to=alfonso@pants.nu \
    /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).