ockam
ockam copied to clipboard
build-trust
Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.
Cache downloads so as to minimise CI download failure https://github.com/ockam-network/ockam/pull/2028/checks?check_run_id=3930692905
If you cd into some of our crates and run `cargo doc`, you'll get warnings (or errors) that the documentation uses links that are no longer valid. For example ```...
Stream client components could use some documentation Stream protocol documentation: https://github.com/ockam-network/proposals/tree/main/design/0009-stream-protocol Example stream client usage: https://github.com/ockam-network/ockam/blob/develop/implementations/elixir/ockam/ockam/lib/ockam/examples/stream/stream.ex
Standard Clone trait is a little ambiguous in sense that one usually expects to have a clone of existing object, while this is not true for our Handle-based and Handle-like...
We probably want to be derive Message trait only explicitly using ```rust #[derive(Message)] ``` Without that, it's very easy to send things not intended to be Messages (happened few times)
[Handle](https://github.com/ockam-network/ockam/tree/ockam_v0.27.0/implementations/rust/ockam/ockam_entity/src/lib.rs#L41) should be moved to ockam_node and used everywhere we interact with Workers in request-response manner (e.g. VaultSync)
Currently BLS dependencies are spread among different crates, which creates unnecessary coupling. Crypto stuff should be isolated in ockam_vault as much as possible
Should be done after #1845
https://github.com/smoltcp-rs/smoltcp --- _If you would like someone to help / mentor / pair program with you as you work on your first Ockam issue, please leave a comment on [this...
Metadata
Owner
Metadata
Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.