TimeStamp: Needs clarification

Bernd Matthes <bernd.matthes@gemplus.com> Wed, 02 May 2001 10:18 UTC

Received: from above.proper.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04777 for <pkix-archive@odin.ietf.org>; Wed, 2 May 2001 06:18:45 -0400 (EDT)
Received: from localhost (daemon@localhost) by above.proper.com (8.9.3/8.9.3) with SMTP id DAA08054; Wed, 2 May 2001 03:18:13 -0700 (PDT)
Received: by mail.imc.org (bulk_mailer v1.12); Wed, 2 May 2001 03:18:10 -0700
Received: from brot.celocom.de (brot.celocom.de [212.78.104.200]) by above.proper.com (8.9.3/8.9.3) with ESMTP id DAA08017 for <ietf-pkix@imc.org>; Wed, 2 May 2001 03:18:08 -0700 (PDT)
Received: from frolic.celocom.de (frolic.celocom.de [212.78.104.90]) by brot.celocom.de (Postfix) with ESMTP id EB4502FD2 for <ietf-pkix@imc.org>; Wed, 02 May 2001 12:17:54 +0200 (CEST)
Received: from gemplus.com (bernd.celocom.de [212.78.104.41]) by frolic.celocom.de (Postfix) with ESMTP id B0ED0108054 for <ietf-pkix@imc.org>; Wed, 2 May 2001 12:17:54 +0200 (CEST)
Message-ID: <3AEFDECE.C500CC29@gemplus.com>
Date: Wed, 02 May 2001 12:17:50 +0200
From: Bernd Matthes <bernd.matthes@gemplus.com>
Organization: Celo Communications -- a Gemplus Company
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: de,en
MIME-Version: 1.0
To: ietf pkix <ietf-pkix@imc.org>
Subject: TimeStamp: Needs clarification
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------msDDCF07E0D2BD0C914A494DBC"
Precedence: bulk
List-Archive: http://www.imc.org/ietf-pkix/mail-archive/
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: mailto:ietf-pkix-request@imc.org?body=unsubscribe

Hi to all!

I need clarification about messageImprint of TimeStampToken.

In <draft-ietf-pkix-time-stamp-14.txt>, Appendix A is written:
"The value of messageImprint field within TimeStampToken shall be a hash
of the value of signature field within SignerInfo for the signedData
being timestamped."

In my opinion is the messageImprint the hash value of the
encryptedDigest
in the SignerInfo (according to RFC2315)
or is the messageImprint the hash value over the message identical to
the
messageDigest in the authenticatedAttributes within the SignerInfo?

Thanks in advance.

-- 
Mors certa, hora incerta. In dubio pro mille.
--------------------------------------------------------------------
Bernd Matthes                   Celo Communications GmbH
Senior Software Engineer    	     - a Gemplus Company
Dipl.-Ing.(FH)                  mailto:bernd.matthes@gemplus.com
--------------------------------------------------------------------
Every information is sensitive information,
and sensitive informations should be protected from being spied.
ergo: because you read this mail you're probably a spy.