Aydin Mercan
14d4569001
* I believe working around `br_sslio_*` isn't worth the effort as the same functionality can be done manually with `*_buf` + `*_ack` which is used by sslio internally. This will especially be useful when wrapping Write/Read traits in std. * Since both server and client contextes use `br_ssl_engine_context`, writing the routines for it removes a lot of future headaches. The engines shouldn't be used directly but will be exposed anyway for special cases and for having more discoverable errors. |
||
---|---|---|
.cargo | ||
.github/workflows | ||
bearssl | ||
bearssl-sys | ||
.gitignore | ||
.gitsigners | ||
.rustfmt.toml | ||
Cargo.lock | ||
Cargo.toml | ||
README.md |
README.md
BearSSL-rs
Use and extend BearSSL in Rust.
Crates
bearssl-sys
: Autogenerated FFI bindings for BearSSL 0.6. Can use the link dynamically or bundle a build itself.- Versions below
0.0.5
are unrelated to this crate.
- Versions below
bearssl
: Higher level code for easier use in servers, clients, etc.- Versions below
0.0.2
are unrelated to this crate.
- Versions below
Development
The code exists in multiple places as listed below:
- Main Repository
- Where the main branch resides.
- CI tasks are planned to run here.
- GitHub Mirror
- Mainly intended to be used as a source for crate registries.
- Short jobs such as auditing also run here.
- Issues here are still considered but PRs will probably be merged manually.
We prefer commit signing via SSH. The allowed signers are listed in .gitsigners
.
To verify, a gitconfig entry such as the following is likely needed:
[gpg.ssh]
allowedSignersFile = .gitsigners
License
All crates in this repository are available under BSD-3-Clause
.
Please refer to each crate's README for more details.