1
# ***** BEGIN LICENSE BLOCK *****
2
# Version: MPL 1.1/GPL 2.0/LGPL 2.1
4
# The contents of this file are subject to the Mozilla Public License Version
5
# 1.1 (the "License"); you may not use this file except in compliance with
6
# the License. You may obtain a copy of the License at
7
# http://www.mozilla.org/MPL/
9
# Software distributed under the License is distributed on an "AS IS" basis,
10
# WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License
11
# for the specific language governing rights and limitations under the
14
# The Original Code is the PKIX-C library.
16
# The Initial Developer of the Original Code is
17
# Sun Microsystems, Inc.
18
# Portions created by the Initial Developer are
19
# Copyright 2004-2007 Sun Microsystems, Inc. All Rights Reserved.
22
# Sun Microsystems, Inc.
24
# Alternatively, the contents of this file may be used under the terms of
25
# either the GNU General Public License Version 2 or later (the "GPL"), or
26
# the GNU Lesser General Public License Version 2.1 or later (the "LGPL"),
27
# in which case the provisions of the GPL or the LGPL are applicable instead
28
# of those above. If you wish to allow use of your version of this file only
29
# under the terms of either the GPL or the LGPL, and not to allow others to
30
# use your version of this file under the terms of the MPL, indicate your
31
# decision by deleting the provisions above and replace them with the notice
32
# and other provisions required by the GPL or the LGPL. If you do not delete
33
# the provisions above, a recipient may use your version of this file under
34
# the terms of any one of the MPL, the GPL or the LGPL.
36
# ***** END LICENSE BLOCK *****
38
This directory contains both sample applications and performance evaluation
43
Currently, there are two performance applications: libpkix_buildThreads and
44
nss_threads. And three sample applications: dumpcert, dumpcrl and
47
============================================================================
49
USAGE: dumpcert <certFile>
50
Parses a certificate located at <certFile> and displays it.
52
Source: <root>/tests/sample_apps/dumpcert.c
53
Binary: <root>/bin/sample_apps/dumpcert
55
============================================================================
57
USAGE: dumpcrl <crlFile>
58
Parses a CRL located at <crlFile> and displays it.
60
Source: <root>/tests/sample_apps/dumpcrl.c
61
Binary: <root>/bin/sample_apps/dumpcrl
63
============================================================================
65
USAGE: validateChain <trustedCert> <cert_1> <cert_2> ... <cert_n>
66
Validates a chain of n certificates using the given trust anchor.
68
Source: <root>/tests/sample_apps/validateChain.c
69
Binary: <root>/bin/sample_apps/validateChain
71
============================================================================
73
PERFORMANCE EVALUATION APPLICATIONS
75
============================================================================
77
USAGE: libpkix_buildthreads <duration> <threads> <eecertNickname>
79
Sets up and runs a PKIX_BuildChain call for the number of seconds
80
specified by <duration> using the number of threads specified by
81
<threads>. This application assumes that the NSS certutil application
82
has already been run to create the NSS databases and that the
83
various nicknames on the command line have been associated with
84
certificates in the NSS databases. The NSS databases MUST reside
85
in the directory where this file is located and MUST be named
86
"cert8.db", "key3.db", and "secmod.db". There must exist a nickname
87
in the databases which has been marked as trusted.
89
Source: <root>/perf/libpkix_buildthreads/libpkix_buildthreads.c
90
Binary: <root>/perf/libpkix_buildthreads/*.OBJ/libpkix_buildthreads
92
============================================================================
94
USAGE: nssThreads <duration> <threads> <eecertNickname>
96
Sets up and runs a CERT_VerifyCertificate call for the number of
97
seconds specified by <duration> using the number of threads specified
98
by <threads>. This application assumes that the NSS certutil
99
application has already been run to create the NSS databases and that
100
the various nicknames on the command line have been associated with
101
certificates in the NSS databases. The NSS databases MUST reside
102
in the directory where this file is located and MUST be named
103
"cert8.db", "key3.db", and "secmod.db". There must exist a nickname in
104
the databases which has been marked as trusted.
106
Source: <root>/perf/nss_threads/nss_threads.c
107
Binary: <root>/perf/nss_threads/*.OBJ/nss_threads
109
============================================================================