From owner-freebsd-questions@FreeBSD.ORG Wed Jun 15 14:08:10 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BB5116A41C for ; Wed, 15 Jun 2005 14:08:10 +0000 (GMT) (envelope-from cblack@securecrossing.com) Received: from mail2.securecrossing.com (209-254-39-195.ip.mcleodusa.net [209.254.39.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E28543D1F for ; Wed, 15 Jun 2005 14:08:09 +0000 (GMT) (envelope-from cblack@securecrossing.com) Received: (qmail 7066 invoked by uid 0); 15 Jun 2005 14:08:09 -0000 Received: from unknown (HELO localhost.localdomain) (cblack@securecrossing.com@127.0.0.1) by mail2.securecrossing.com with SMTP; 15 Jun 2005 14:08:09 -0000 From: Christopher Black To: Brian Henning In-Reply-To: <47f8d931050614145288f9333@mail.gmail.com> References: <47f8d931050614145288f9333@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-bEtCHXNTfjcfXiEtzYIE" Organization: Secure Crossing Date: Wed, 15 Jun 2005 10:08:03 -0400 Message-Id: <1118844483.18754.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Cc: FreeBSD Questions Subject: Re: OT: GnuPG X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 14:08:10 -0000 --=-bEtCHXNTfjcfXiEtzYIE Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2005-06-14 at 16:52 -0500, Brian Henning wrote: > Greetings: >=20 > When I run gnupg using the same rsa key on the same input file I > noticed that it returns different cipher text files as resuts. Both > the cipher files decrypt to the same plain text file just fine. Can > someone explain to my why that is the cipher text is different? >=20 > Thanks, >=20 > Brian The way GnuPG works in public key mode (ie: RSA) is by encrypting the data with a random symmetric session key, then encrypting that session key with the public key you choose. The reason for this is that symmetric encryption is much easier to do, and far more secure than asymmetric (public-key) encryption for any given key-size. Also, if you're encrypting a file to 10 different people, this way you can just encrypt the symmetric keys with 10 separate public keys, and attach them to the actual encrypted file, instead of having 10 seperate encrypted files. When the file could be hundreds of megabytes, this is a huge resource saver. --=20 Christopher Black Chief Security Engineer Secure Crossing 22750 Woodward Suite 304 - Ferndale, MI 48220 Tel (800) 761-4299 | Direct (248) 658-6120 cblack@securecrossing.com | www.securecrossing.com --=-bEtCHXNTfjcfXiEtzYIE Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCsDZDAPxZlIbJ6AwRAryRAKCABRNBg+hp0THBOMK0h3vjK90FoACfbwmP mWekA1KW974SamqGrvVdn1o= =kBkw -----END PGP SIGNATURE----- --=-bEtCHXNTfjcfXiEtzYIE--