I'm in the process of adding CSR support to the NSS python binding and
I'm not sure I fully follow how CSR attributes are handled so I'm
looking for some clarification.
From reading the relevant RFC's my understanding is that a CSR contains
a sequence of attributes and an attribute has a type
I have a question for CAs that accept PKCS#10 CSRs.
Background:
PKCS#10 certificate requests may contain an optional set of ATTRIBUTEs.
One type of ATTRIBUTE, the only type mentioned in PKCS#10, is the PKCS#9
certificate Extension Request. But PKCS#10 suggests that other types
could be defined,
If I'm coding a PKCS#11 module, how exactly the -string parameter
from modutil gets passed down to the library?
i.e.,
$ modutil -add mylib -libfile /lib/mylib.so -string my conf string
I though C_Initialize, OpenSession or even InitToken at first,
but looking at the spec I couldn't immediately
On 2010-06-17 13:45 PDT, Klaus Heinrich Kiwi wrote:
If I'm coding a PKCS#11 module, how exactly the -string parameter
from modutil gets passed down to the library?
i.e.,
$ modutil -add mylib -libfile /lib/mylib.so -string my conf string
I though C_Initialize, OpenSession or even InitToken
On 06/17/2010 04:18 PM, Nelson B Bolyard wrote:
On 2010-06-17 13:45 PDT, Klaus Heinrich Kiwi wrote:
If I'm coding a PKCS#11 module, how exactly the -string parameter
from modutil gets passed down to the library?
i.e.,
$ modutil -add mylib -libfile /lib/mylib.so -string my conf string
I
On 2010-06-17 05:58 PDT, John Dennis wrote:
I'm in the process of adding CSR support to the NSS python binding and
I'm not sure I fully follow how CSR attributes are handled so I'm looking
for some clarification.
Look at how certutil does it. That's best example we have right now.
From
6 matches
Mail list logo
