> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kaur Virunurm
> Sent: Thursday, September 23, 1999 09:10 AM
> To: [EMAIL PROTECTED]
> Subject: Re: signed and certified but not for email
>

> Won't the certificate usage in IE also depend on the KEY properties?
>
> xenroll control has KeySpec property that you can specity
> before CreatePKCS10():
>       xenroll.KeySpec          = 1     ' AT_KEYEXCHANGE
>       xenroll.KeySpec          = 2     ' AT_SIGNATURE

I use:
    Enroll.KeySpec = 1
    Enroll.GenKeyFlags = 3
    document.data.reqEntry.value = Enroll.CreatePKCS10(DNName,
"1.3.14.3.2.29")

I see that AT_SIGNATURE is used for signing messages and often has a large
key size even under export versions of IE.

Is AT_KEYEXCHANGE used for encrypting email messages?  I would like to use
an escrowable key for encyption (so we can recover employees work-related
messages) but don't particularly want to have the ability to impersonate
employees.

> As I understand, this should change allowable key usages and might
> give the effects that you see? Just a guess - but play with this
> property and see if it has any effects.

I played with this severely last year and the settings I have worked then.
As per another message here it seems that maybe IE is getting the wrong
idea.

Perhaps I could export the certificate and get someone to look at it and see
what it is really set as, so we can see what is lying.

?

Thanks

Sam

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to