package pkcs11

Build not checked
  1. Overview
  2. Docs

Description

This library contains ctypes bindings to the PKCS#11 API.

This API is used by smartcards and Hardware Security Modules to perform cryptographic operations such as signature or encryption.

Tags

org:cryptosense

Added to opam-repository:

README

Pkcs11 - bindings to the PKCS#11 cryptographic API Build Status docs

PKCS11 is an API used by smartcards and Hardware Security Modules to perform cryptographic operations such as signature or encryption.

This library contains two parts: type definitions corresponding to the PKCS#11 API, and bindings using ctypes to emit calls to a DLL.

To install the driver part, install ctypes and ctypes-foreign - it will build a pkcs11.driver package.

The entry point of this library is [P11.load_driver]. An example is available in test/example_sign.ml.

Dependencies (10)

  1. topkg build
  2. ocamlfind build
  3. ocamlbuild build
  4. yojson < "2.0.0"
  5. ppx_deriving_yojson >= "3.0"
  6. ppx_deriving >= "4.0"
  7. key-parsers >= "0.5.0" & != "0.6.0" & < "1.0.0"
  8. integers < "0.5.0"
  9. hex >= "1.0.0"
  10. ocaml >= "4.02.0"

Dev Dependencies (1)

  1. ounit with-test

Optional Dependencies (3)

  1. ctypes-foreign
  2. ctypes
  3. cmdliner

Used by

None

Conflicts (2)

  1. ctypes >= "0.18.0"
  2. ctypes < "0.12.0"

Build status

Results of building pkcs11 with each compiler on check.ci.ocaml.org, run of against opam-repository 8d8d144. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

This version is not in the latest run; the versions below are.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
1.0.1 good good good n/a n/a
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure