37 releases (21 stable)

8.0.0-alpha Feb 7, 2024
7.5.1 Apr 16, 2024
7.5.0 Mar 14, 2024
7.4.0 Oct 9, 2023
1.0.1 Jan 17, 2020

#69 in Cryptography

Download history 1987/week @ 2024-02-15 2029/week @ 2024-02-22 1621/week @ 2024-02-29 1788/week @ 2024-03-07 2087/week @ 2024-03-14 1414/week @ 2024-03-21 1255/week @ 2024-03-28 1305/week @ 2024-04-04 1379/week @ 2024-04-11 1476/week @ 2024-04-18 1538/week @ 2024-04-25 1890/week @ 2024-05-02 1782/week @ 2024-05-09 1606/week @ 2024-05-16 1570/week @ 2024-05-23 1409/week @ 2024-05-30

6,791 downloads per month
Used in 16 crates (11 directly)

Apache-2.0

3.5MB
101K SLoC

TPM2 Software Stack Rust Wrapper

Crates.io Code documentation

This is the high-level, Rust idiomatic wrapper crate that exposes an interface to TSS.

This crate depends on the tss-esapi-sys crate for its FFI interface. By default, pre-generated bindings are used. If you'd like the bindings to be generated at build time, please enable either the generate-bindings feature - the FFI bindings will then be generated at build time using the headers identified on the system.

Our end-goal is to achieve a fully Rust-native interface that offers strong safety and security guarantees. Check out our documentation for an overview of our code safety approach.

Cargo Features

The crate currently offers the following features:

  • generate_bindings - forces the underlying tss-esapi-sys crate to regenerate the FFI bindings on each build, using the TSS libraries available on the build machine.
  • abstraction (enabled by default) - provides a set of abstracted primitives on top of the basic Rust-native ESAPI API provided by the crate. This feature can be turned off to reduce the number of dependencies built.

Cross compiling

For more information on cross-compiling the tss-esapi crate, please see the README of the tss-esapi-sys crate.

Copyright 2021 Contributors to the Parsec project.

Dependencies

~2.9–5MB
~90K SLoC