~ubuntu-branches/ubuntu/trusty/xulrunner/trusty

1.1.12 by Devid Antonio Filoni
Import upstream version 1.8.1.16+nobinonly
1
This is a very trivial program that loads and excercises a PKCS#11
2
module, trying basic operations.  I used it as a basic check that
3
my data-only modules for NSS worked, and I'm including it here as
4
a first sample test program.
5
6
7
This program uses GNU autoconf: run ./configure --help for info.
8
In addition to the standard options, the configure script accepts
9
the following:
10
11
  --with-nspr[=path]      specify location of NSPR
12
  --with-nss-dist[=path]  specify path to NSS dist directory
13
  --with-nss-hdrs[=path]  or, specify path to installed NSS headers
14
  --with-rsa-hdrs[=path]  if not using NSS, specify path to RSA headers
15
  --disable-debug         default is enabled
16
17
This program uses NSPR; you may specify the path to your NSPR 
18
installation by using the "--with-nspr" option.  The specified
19
directory should be the one containing "include" and "lib."
20
If this option is not given, the default is the usual prefix
21
directories; see ./configure --help for more info.
22
23
This program requires either the pkcs11*.h files from RSA, or
24
the NSS equivalents.  To specify their location, you must
25
specify one of --with-nss-dist, --with-nss-hdrs, or --with-rsa-hdrs.
26
27
If you have an NSS build tree, specify --with-nss-dist and provide
28
the path to the mozilla/dist/*.OBJ directory.  (If you got this
29
package by checking it out from mozilla, it should be about six
30
directories up, once you've built NSS.)
31
32
Alternatively, if you have an NSS installation (including "private"
33
files, e.g. "ck.h") you may point directly to the directory containing
34
the headers with --with-nss-hdrs.
35
36
If you would rather use the RSA-provided header files, or your own
37
versions of them, specify their location with --with-rsa-hdrs.
38
39
The flag --disable-debug doesn't really do much here other than
40
exclude the CVS_ID info from the binary.
41
42
43
To run the program, specify the name of the .so (or your platform's
44
equivalent) containing the module to be tested, e.g.: 
45
46
  ./trivial ../../../../../../dist/*.OBJ/lib/libnssckbi.so
47
48
49
If you're using NSS, and using our experimental "installer's
50
arguments" fields in CK_C_INITIALIZE_ARGS, you can specify an
51
"installer argument" with the -i flag:
52
53
  ./trivial -i ~/.netscape/certs.db [...]/libnssckdb.so
54
55
56
Share and enjoy.