Re: Importing CRL using NSS API

2006-05-30 Thread Nelson B. Bolyard
Wan-Teh Chang wrote: > Paul, > > The code in mozilla/security/nss/cmd/lib is > intended for use by the NSS command-line tools > only. This is why the header file secutil.h, > which declares those SECU_ funcitons, is marked > "private", and the static library libsectool.a > (sectool.lib) is not pa

Re: Importing CRL using NSS API

2006-05-30 Thread Paul Neyman
Julien Pierre wrote: [EMAIL PROTECTED] wrote: Hi! I'm trying to import a CRL (in DER format) using NSS API. Since 3.4 API does not have an import function available, I took the source code from the crlutil and massaged it to fit into our application. NSS 3.4 did have import functions avai

Re: Importing CRL using NSS API

2006-05-30 Thread Paul Neyman
Hi Nelson, > Another use of "public" and "private" involves the intentions of the > software developers. In that sense, "public" means "the software developers > intended for other people (other software) to use this symbol" and > "private" means "the software developers intended for this symbo

Re: Importing CRL using NSS API

2006-05-30 Thread Julien Pierre
[EMAIL PROTECTED] wrote: Hi! I'm trying to import a CRL (in DER format) using NSS API. Since 3.4 API does not have an import function available, I took the source code from the crlutil and massaged it to fit into our application. NSS 3.4 did have import functions available for CRLs : CERT_Im

Re: Importing CRL using NSS API

2006-05-30 Thread Wan-Teh Chang
Paul, The code in mozilla/security/nss/cmd/lib is intended for use by the NSS command-line tools only. This is why the header file secutil.h, which declares those SECU_ funcitons, is marked "private", and the static library libsectool.a (sectool.lib) is not part of the NSS binary distributions.

Re: Importing CRL using NSS API

2006-05-30 Thread Nelson B. Bolyard
Paul Neyman wrote: > Thanks for the quick reply. Let me clear up myself. Here's what's > happening: >>> The crlutil code, however, uses method SECU_ReadDERFromFile, which is >>> not exported as public, and I get a failure during linking stage trying >>> to use sectool.lib. > >> Um, it's not? >

Re: Importing CRL using NSS API

2006-05-30 Thread Paul Neyman
Hi, Nelson! Thanks for the quick reply. Let me clear up myself. Here's what's happening: You're using NSS 3.4? The current NSS is 3.11 . I am using NSS 3.11, the 3.4 I was referring to is from the list of public methods on Mozilla page (http://www.mozilla.org/projects/security/pki/nss/nss-3