polyproto

Crate supplying (generic) Rust types and traits to quickly get a polyproto implementation up and running.

Implementing polyproto

The crate is currently in an alpha stage. Some functionality is missing, and things may break or change at any point in time.

This crate extends upon types offered by der and spki. As such, these crates are required dependencies for projects looking to implement polyproto.

Start by implementing the trait crate::signature::Signature for a signature algorithm of your choice. Popular crates for cryptography and signature algorithms supply their own PublicKey and PrivateKey types. You should extend upon these types with your own structs and implement the crate::key traits for these new structs.

You can then use the crate::certs types to build certificates using your implementations of the aforementioned traits.

View the examples directory for a simple example on how to implement and use this crate.

Cryptography

This crate provides no cryptographic functionality whatsoever; its sole purpose is to aid in implementing polyproto by transforming the polyproto specification into well-defined yet adaptable Rust types.

[dependencies]
polyproto = { version = "0", features = ["wasm"] }

WebAssembly

This crate is designed to work with the wasm32-unknown-unknown target. To compile for wasm, you will have to use the wasm feature:

reqwest

By default, this crate uses reqwest for HTTP requests. reqwest is an optional dependency, and you can disable it by using polyproto with default-features = false in your Cargo.toml:

[dependencies]
polyproto = { version = "0", default-features = false, features = ["routes"] }

Disabling reqwest gives you the ability to use your own HTTP client.