Skip to content

YubicoLabs/pkcs11test

This branch is 38 commits ahead of, 39 commits behind google/pkcs11test:dev.

Folders and files

NameName
Last commit message
Last commit date
Dec 16, 2016
Feb 27, 2017
Nov 10, 2014
Dec 16, 2016
Sep 18, 2014
Dec 16, 2016
Nov 12, 2014
Dec 14, 2022
Oct 8, 2014
Jan 22, 2024
Nov 12, 2014
Nov 12, 2014
Dec 16, 2016
Feb 6, 2025
Dec 16, 2016
Oct 8, 2014
Jul 20, 2016
Oct 14, 2014
Dec 16, 2016
Sep 26, 2017
Nov 12, 2014
Oct 1, 2014
Oct 1, 2014
Sep 18, 2014
Jul 20, 2016
Dec 14, 2022
Jan 4, 2017
Oct 16, 2014
Feb 27, 2017
Jan 22, 2024
Nov 12, 2014
Dec 16, 2016

Repository files navigation

pkcs11Test: A PKCS#11 Test Suite

Travis

Warning: Do not run this test suite against a PKCS#11 token that contains real data; some of the tests may erase or permanently lock the token.

This repository holds a test suite for, and is therefore derived from, the RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki).

To build the test program on Linux, just run make. To run the tests against common Linux PKCS#11 implementations:

This is NOT an official Google product.

Test Options

The test program requires the following command-line parameters to be set:

  • -m libname: Provide the name of the PKCS#11 library to test.
  • -l libpath: Provide the path holding the PKCS#11 library.

There are also several optional command-line parameters:

  • -s slotid: Provide the slot ID that will be used for the tests
  • -v: Generate verbose output.
  • -u pwd: Provide the user PIN/password.
  • -o pwd: Provide the security officer PIN/password.
  • -I: Perform token initialization tests. This will wipe the contents of the PKCS#11 token

The test program uses Google Test, and the Google Test command line options are also available. In particular, --gtest_filter=<filter> can be used to run a subset of the tests.

Releases

No releases published

Packages

No packages published

Languages

  • C++ 86.2%
  • Python 10.7%
  • CMake 0.7%
  • Shell 0.7%
  • Makefile 0.6%
  • M4 0.6%
  • C 0.5%