RE: Signing Untrusted SCVP?

Stephen Kent <kent@bbn.com> Mon, 05 April 2004 19:35 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29344 for <pkix-archive@lists.ietf.org>; Mon, 5 Apr 2004 15:35:25 -0400 (EDT)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.8) with ESMTP id i35I900Y096852; Mon, 5 Apr 2004 11:09:00 -0700 (PDT) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i35I90Iv096851; Mon, 5 Apr 2004 11:09:00 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from aragorn.bbn.com (aragorn.bbn.com [128.33.0.62]) by above.proper.com (8.12.11/8.12.8) with ESMTP id i35I8xs7096829 for <ietf-pkix@imc.org>; Mon, 5 Apr 2004 11:08:59 -0700 (PDT) (envelope-from kent@bbn.com)
Received: from [128.89.89.75] (dhcp89-089-075.bbn.com [128.89.89.75]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id i35I8t7Z023928; Mon, 5 Apr 2004 14:08:57 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po2.bbn.com
Message-Id: <p06020410bc974f8a26e6@[128.89.89.75]>
In-Reply-To: <20040403040323.M36717@orionsec.com>
References: <DE909E05406F3340B186DA5A410B05F642A286@mongo.corestreet.com> <20040403040323.M36717@orionsec.com>
Date: Mon, 05 Apr 2004 14:04:21 -0400
To: Santosh Chokhani <chokhani@orionsec.com>
From: Stephen Kent <kent@bbn.com>
Subject: RE: Signing Untrusted SCVP?
Cc: ietf-pkix@imc.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Sender: owner-ietf-pkix@mail.imc.org
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>

At 12:03 AM -0400 4/3/04, Santosh Chokhani wrote:
>Steve:
>
>I do not see a particular reason to require a DPD Server to be held to a
>higher standard then a Directory Server.  We do not require signed responses
>from Directories.  Both being stationary servers, are equally prone to
>hacking.  Also, in order to verify the DPD Server signature, the client may
>get into another problem of obtaining a path for the DPD Server itself, which
>may not be a circular problem, but will degrade performance

We are not the LDAP WG, so we don't make requirements for directory 
access, as I noted in my previous message.  (Our last foray into that 
area is a superceded RFC that had mixed feelings about DoS issues.)

I thought there was a clear need to configure clients with an ability 
to directly verify signatures for DPD and DPV servers. Otherwsie, as 
you note, a circular dependency can arise.

Steve