RE: secure sign & encrypt
"Dominikus Scherkl" <Dominikus.Scherkl@glueckkanja.com> Thu, 23 May 2002 12:04 UTC
Received: from above.proper.com (mail.imc.org [208.184.76.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05529 for <openpgp-archive@lists.ietf.org>; Thu, 23 May 2002 08:04:22 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id g4NBqKg23444 for ietf-openpgp-bks; Thu, 23 May 2002 04:52:20 -0700 (PDT)
Received: from guk1d002.glueckkanja.org (mail.glueckkanja.com [62.8.243.3]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g4NBqIL23440 for <ietf-openpgp@imc.org>; Thu, 23 May 2002 04:52:19 -0700 (PDT)
content-class: urn:content-classes:message
Subject: RE: secure sign & encrypt
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 23 May 2002 13:52:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <2F89C141B5B67645BB56C038537578821B58C9@guk1d002.glueckkanja.org>
Thread-Topic: secure sign & encrypt
Thread-Index: AcICOijLTUSjlZnGRoy3/gCC46m2kgAEtPHg
From: Dominikus Scherkl <Dominikus.Scherkl@glueckkanja.com>
To: ietf-openpgp@imc.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id g4NBqJL23441
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>
Content-Transfer-Encoding: 8bit
Hi. > Well, I intended it to become an atomic function. Nice. And how? Common public key cryptography doesn't provide algorithms to sign an encrypt in a single, undividable step. I see no other way than "encrypt, sign and encrypt" (ESE) to archive all cyptografic goals which seems inportant to me: Two goals require ES: - to ensure that the reciever cannot forward a message without destroying the signature or reveiling that it was originaly send to him for his eyes only we must sign after encryption. - to convince the receiver he was the original target we also need to first encryt and than sign. two further goals require SE: - to ensure the signature is not used for another message we must first sign than encrypt (else especialy for RSA there exist a choosen key attack). - to hide that you are sending signed messages you also need to do encryption as the very last step. The easiest way to archive all four is ESE, an it is worth the time cost of two encryptions, I think. Best Regards. -- Dominikus Scherkl dominikus.scherkl@glueckkanja.com
- secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Hal Finney
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt vedaal
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Derek Atkins
- Re: secure sign & encrypt vedaal
- Re: secure sign & encrypt Derek Atkins
- Re: secure sign & encrypt vedaal
- Re: secure sign & encrypt Jon Callas
- RE: secure sign & encrypt Terje Braaten
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt vedaal
- Re: secure sign & encrypt Derek Atkins
- RE: secure sign & encrypt Terje Braaten
- RE: secure sign & encrypt Terje Braaten
- RE: secure sign & encrypt Hal Finney
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Jon Callas
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Derek Atkins
- Re: secure sign & encrypt Peter Gutmann
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Matthew Byng-Maddick
- RE: secure sign & encrypt Dominikus Scherkl
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Derek Atkins
- Re: secure sign & encrypt Derek Atkins
- Re: secure sign & encrypt Derek Atkins
- RE: secure sign & encrypt Terje Braaten
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt David P. Kemp
- Re: secure sign & encrypt Derek Atkins
- Re: secure sign & encrypt Matthew Byng-Maddick
- RE: secure sign & encrypt Terje Braaten
- RE: secure sign & encrypt Dominikus Scherkl
- RE: secure sign & encrypt Dominikus Scherkl
- Re: secure sign & encrypt disastry
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt disastry
- Re: secure sign & encrypt Derek Atkins
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Derek Atkins
- RE: secure sign & encrypt Terje Braaten
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Derek Atkins
- Re: secure sign & encrypt Derek Atkins
- RE: secure sign & encrypt Terje Braaten
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Peter Gutmann
- Re: secure sign & encrypt Michael Young
- Re: secure sign & encrypt Paul Hoffman / IMC
- RE: secure sign & encrypt Terje Braaten
- Re: secure sign & encrypt Brian M. Carlson
- Re: secure sign & encrypt Jon Callas
- Re: secure sign & encrypt Adrian 'Dagurashibanipal' von Bidder
- RE: secure sign & encrypt john.dlugosz
- RE: secure sign & encrypt Terje Braaten