Re: draft-ietf-pkix-rfc3770bis-01: key usage extension
Russ Housley <housley@vigilsec.com> Thu, 14 April 2005 18:27 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 OAA09328 for <pkix-archive@lists.ietf.org>; Thu, 14 Apr 2005 14:27:23 -0400 (EDT)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j3EHlGLo044223; Thu, 14 Apr 2005 10:47:16 -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 j3EHlGp8044222; Thu, 14 Apr 2005 10:47:16 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [144.202.243.4]) by above.proper.com (8.12.11/8.12.9) with SMTP id j3EHlFTJ044213 for <ietf-pkix@imc.org>; Thu, 14 Apr 2005 10:47:15 -0700 (PDT) (envelope-from housley@vigilsec.com)
Received: (qmail 17861 invoked by uid 0); 14 Apr 2005 17:24:49 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (138.88.97.235) by woodstock.binhost.com with SMTP; 14 Apr 2005 17:24:49 -0000
Message-Id: <6.2.0.14.2.20050414132213.039a9ae0@mail.binhost.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Thu, 14 Apr 2005 13:24:48 -0400
To: Peter Sylvester <Peter.Sylvester@edelweb.fr>, Peter.Sylvester@edelweb.fr
From: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-ietf-pkix-rfc3770bis-01: key usage extension
Cc: ietf-pkix@imc.org
In-Reply-To: <200504141636.j3EGafb02347@chandon.edelweb.fr>
References: <200504141636.j3EGafb02347@chandon.edelweb.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
Peter: > > > > >2 *** > > > > > > > > > > If a certificate contains a key usage extension, the KeyUsage bits > > > > > that are needed depends on the EAP method that is employed; > however, > > > > > the keyCertSign bit and the cRLSign MUST NOT be associated > with EAP > > > > > method end entity certificates. > > > > > > > > > >This means that you cannot have a certificat WITHOUT keyUsage? > > > > >Or, in case of a certificate without keyUsage, you could use it > > > > >for CrlSigning? > > > > > > > > No. The paragraph only talks about the key usage extension in > support of > > > > EAP methods. The question you are asking is beyond the scope of the > > > > paragraph and the whole document. > > > > > > > > > >oops, I made a mistake. i wanted to ask "could you use a certificate > > >that has no keyUsage for EAP methods?' > > > > Yes. In this case, the certificate is not providing any constraints on > the > > key usage. > > > > Russ > >take a cert with all bit on. This is equivalent to having no keyUsage at all >as far as I remember. in this case the keyCertSign bit and the cRLSign are >set, >and the above 'MUST NOT' prohibits use of this cert. is this what you intend? >I don't think so. > >Isn't the right wording: no known EAP usage requires keyCertSign or cRLSign? How about: ... however, EAP methods MUST NOT require the keyCertSign bit or the cRLSign to be set in end entity certificates. Russ
- Re: draft-ietf-pkix-rfc3770bis-01: key usage exte… Peter Sylvester
- Re: draft-ietf-pkix-rfc3770bis-01: key usage exte… Russ Housley
- Re: draft-ietf-pkix-rfc3770bis-01: key usage exte… Peter Sylvester
- Re: draft-ietf-pkix-rfc3770bis-01: key usage exte… Russ Housley
- Re: draft-ietf-pkix-rfc3770bis-01: key usage exte… Peter Sylvester
- Re: draft-ietf-pkix-rfc3770bis-01: key usage exte… Peter Sylvester