Subject: AW: Question from a new comer about KeyUsage

From: [email-masked]
Date: Thu, 22 Mar 2001 10:14:14 +0100

Hi Prashant,

Neither way, but 03 03 07 00 80 would formaly be correct.
(You have to count bits in the Bitstring from left to right.)

BUT this makes NO sense in this context, as bits 7 and 8
are undefined in the absence of the keyAgreement bit.
(See RFC 2459.)

Regards, Stefan

> -----Ursprüngliche Nachricht-----
> Von: Prashant Kumar [mailto:[email-masked]]
> Gesendet am: Mittwoch, 21. März 2001 18:55
> An: 'Stefan.Heiss'
> Betreff: RE: Question from a new comer about KeyUsage
>
> Stefan,
>
> Thanks a lot for your help. How will I encode
> bit 8(ie, the 9th bit) in keyusage using BER.
> Will it be.
>
> 03 03 00 00 01 or 03 03 0E 80 00.
>
> Thank you again.
>
> Regards,
> Prashant.
>
> -----Original Message-----
> From: Stefan Heiss [mailto:[email-masked]]
> Sent: Wednesday, March 21, 2001 12:29 PM
> To: Kumar, Prashant [CENTR:437:EXCH]
> Subject: AW: Question from a new comer about KeyUsage
>
>
> 05 means: ignore the last 5 bits of following the bitstream.
> A0 is the whole bitstream, i.e. bit 0 and 2 are set.
>
> Regards Stefan
>
>
> Dr. Stefan Heiss
> BROKAT AG | Commerce Systems | Research & Development
> Ringstrasse 33 | D-04430 Dölzig
> Phone: +49 (34205) 61-648 | Fax: -535
> <http://www.brokat.com/>
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Prashant Kumar [mailto:[email-masked]]
> > Gesendet am: Mittwoch, 21. März 2001 17:26
> > An: [email-masked]
> > Betreff: Question from a new comer about KeyUsage
> >
> > In one of the Microsoft Certificate the Key usage bits are
> > set as 0x05 A0(0000 0101 1010 0000). If we open the
> > certificate using MS it claims that
> >
> > 1. Digital Signature, Key Encipherment[A0] bits are set.
> >
> > However if you go according to the RFC 2459 it actually has
> > Digital Signature, nonRepudiation, and dataEncipherment set
> > ....(Bits 0, 1 and 3) bit 8 is the right most bit...
> >
> > KeyUsage ::= BIT STRING {
> > digitalSignature (0),
> > nonRepudiation (1),
> > keyEncipherment (2),
> > dataEncipherment (3),
> > keyAgreement (4),
> > keyCertSign (5),
> > cRLSign (6),
> > encipherOnly (7),
> > decipherOnly (8) }
> >
> > Any Comments ?
> >
> > Regards,
> > Prashant.
> >
> >
>
>
>