| .. | ||
| debian | ||
| examples | ||
| proto | ||
| service | ||
| src | ||
| utils/ctl | ||
| build.rs | ||
| Cargo.toml | ||
| CHANGELOG | ||
| g3keymess.spec | ||
| README.md | ||
g3keymess
g3keymess is a server implementation of Cloudflare Keyless protocol.
How to build
You need to follow the dev-setup guide to set up your build environment first.
To build debug binaries:
cargo build -p g3keymess -p g3keymess-ctl
To build release binaries:
cargo build --profile release-lto -p g3keymess -p g3keymess-ctl
See Packaging if you want to build binary packages or docker images.
Features
g3keymess dynamically links to libcrypto on the system as the crypto engine by default.
You can specify the following feature flags to try other crypto engines:
-
vendored-openssl
Use the latest OpenSSL.
-
vendored-boringssl
Use BoringSSL.
-
vendored-tongsuo
Use Tongsuo.
Hardware
It's possible to use hardware crypto engines by using OpenSSL PROVIDERS.
Use the following compilation feature flags:
cargo build --features openssl-async-job
The system default libcrypto should be used, and the hardware engine should be compiled against it also.
The hardware engine should be enabled in openssl.cnf. If you don't want
to change the default openssl.cnf, you can create a new one and export it as environment variable OPENSSL_CONF.
Examples
See examples directory.