17 unstable releases (6 breaking)
✓ Uses Rust 2018 edition
|new 0.19.2||Jan 17, 2020|
|0.18.1||Jan 5, 2020|
|0.18.0||Dec 22, 2019|
|0.18.0-alpha.1||Oct 27, 2019|
|0.1.1||Sep 25, 2017|
#136 in Network programming
97 downloads per month
Trust-DNS Util is a support library for the Trust-DNS libraries.
This will take a private DNSKEY as generated by BIND9 and output an OpenSSL compatible PEM formatted file. WARNING this will contain private key material.
$ cargo run --bin pem-to-public-dnskey -- --help Trust-DNS dnskey-to-pem 0.11.3 Benjamin Fry <email@example.com> Converts a dnskey, as generated from BIND's dnssec-keygen, into pem format USAGE: dnskey-to-pem [OPTIONS] <PRIVATE_KEY_FILE> FLAGS: -h, --help Prints help information -V, --version Prints version information OPTIONS: -o, --output <OUTPUT_FILE> Output FILE to write to [default: out.pem] ARGS: <PRIVATE_KEY_FILE> Input FILE from which to read the DNSSec private key
This utility can be used to output raw bytes in the DNSKEY RDATA format. This is useful for associating custom public keys with the TrustAnchor facility in Trust-DNS.
$ cargo run --bin pem-to-public-dnskey -- --help Trust-DNS pem-to-public-dnskey 0.11.3 Benjamin Fry <firstname.lastname@example.org> Converts a PEM formatted pubblic key into a raw public dnskey (this is not the inverse of bind_dnskey_to_pem). This can be used to create a dnskey in the TrustAnchor internal format. USAGE: pem-to-public-dnskey [OPTIONS] <PEM_KEY_FILE> FLAGS: -h, --help Prints help information -V, --version Prints version information OPTIONS: -o, --output <OUTPUT_FILE> Output FILE to write to [default: out.dnskey] ARGS: <PEM_KEY_FILE> Input PEM FILE from which to read the public key
Trust-DNS does it's best job to follow semver. Trust-DNS will be promoted to 1.0 upon stabilization of the publicly exposed APIs. This does not mean that Trust-DNS will necessarily break on upgrades between 0.x updates. Whenever possible, old APIs will be deprecated with notes on what replaced those deprecations. Trust-DNS will make a best effort to never break software which depends on it due to API changes, though this can not be guaranteed. Deprecated interfaces will be maintained for at minimum one major release after that in which they were deprecated (where possible), with the exception of the upgrade to 1.0 where all deprecated interfaces will be planned to be removed.