You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the high-level, Rust idiomatic wrapper crate that exposes an interface
9
+
This is the high-level, Rust idiomatic wrapper crate that exposes an interface
10
10
to [TSS](https://github.com/tpm2-software/tpm2-tss).
11
11
12
12
This crate depends on the [`tss-esapi-sys`](../tss-esapi-sys/) crate for its
13
13
FFI interface. By default, pre-generated bindings are used. If you'd like the
14
-
bindings to be generated at build time, please enable either the
14
+
bindings to be generated at build time, please enable either the
15
15
`generate-bindings` feature - the FFI bindings will then be generated at build
16
16
time using the headers identified on the system.
17
17
@@ -31,7 +31,7 @@ The crate currently offers the following features:
31
31
*`abstraction` (enabled by default) - provides a set of abstracted primitives
32
32
on top of the basic Rust-native ESAPI API provided by the crate. This feature
33
33
can be turned off to reduce the number of dependencies built.
34
-
*`serde` - enable serde `Serialize`/`Deserialize` traits for types.
34
+
*`serde` - enable serde `Serialize`/`Deserialize` traits for types.
35
35
*`rustcrypto-full` (disabled by default) - provides conversion from all
36
36
supported elliptic curves, rsa or hashes.
37
37
Support for individual hash, rsa or curves can be pulled individually.
@@ -45,4 +45,11 @@ The crate currently offers the following features:
45
45
46
46
For more information on cross-compiling the `tss-esapi` crate, please see the README of the `tss-esapi-sys` crate.
47
47
48
+
## Building against libtss2
49
+
50
+
The [TSS](https://github.com/tpm2-software/tpm2-tss) library can be installed from Debian, RPM, or other packaging manager.
51
+
It will install a pkg-config definition to indicate how to compile and link against the library.
52
+
When it is installed via source, and/or if it has been edited (such as to debug things), then the version number will be marked with the git commit (and dirty flag). The resulting version string is unfortunately not compatible with the semver parser/comparing mechanism, and it can be rejected.
53
+
Setting the environment variable TPM2\_TSS\_VERSION\_IGNORE\]_PRERELEASE to a non-empty string will cause the build system to ignore this pre-release information.
54
+
48
55
*Copyright 2021 Contributors to the Parsec project.*
0 commit comments