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

#74 in Cryptography

Download history 1827/week @ 2024-01-10 1803/week @ 2024-01-17 2016/week @ 2024-01-24 1595/week @ 2024-01-31 1739/week @ 2024-02-07 1919/week @ 2024-02-14 1912/week @ 2024-02-21 1858/week @ 2024-02-28 1540/week @ 2024-03-06 2257/week @ 2024-03-13 1567/week @ 2024-03-20 1106/week @ 2024-03-27 1361/week @ 2024-04-03 1366/week @ 2024-04-10 1482/week @ 2024-04-17 1103/week @ 2024-04-24

5,658 downloads per month
Used in 15 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

~3.5–5.5MB
~105K SLoC