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.
In the `ockam_macros` crate, we require basically every feature of `syn` (by way of requiring `full` and `extra-traits`): https://github.com/ockam-network/ockam/blob/5a84ea59fd9d8a67b8e0585a6be312c6d54fc906/implementations/rust/ockam/ockam_macros/Cargo.toml#L32 This is probably more than we need, and slows down our...
This is essentially the same as #2288, but for `ockam_key_exchange_core`. We're trying to reduce the number of crates, and part of that is moving `ockam_key_exchange_core` into a new `key_exchange` submodule...
*Note: This must be done after #2288. Alternatively, it can be done at the same time as it, if the same person wants to do both at the same time.*...
Latests MacOS release uses port 5000 for some service, therefore guides that use that port won't work
This function can send more than one message, we should call in something else, maybe `send_message_and_process_queue` https://github.com/ockam-network/ockam/blob/356efed1b3f9f08d63a84694cc7ac723af4ff744/implementations/elixir/ockam/ockam/lib/ockam/messaging/ordering/strict/index_pipe.ex#L79-L83
The `signature_core` crate has a couple issues related to import/exports: 1. First, it should just be unconditionally `no_std`. It doesn't declare any features, but has https://github.com/ockam-network/ockam/blob/cc93b3863df2f8343c824ace8b30041bae2fa8f2/implementations/rust/ockam/signature_core/src/lib.rs#L11-L17, so this could just...
In `ockam_core` we re-export several libraries that we don't need to. We should clean this up. Specifically: --- ```rs pub extern crate hex; ``` Anything that needs `hex` should be...
Many of our Cargo.toml files have some slightly odd formatting for dependency lists. Often this is either: 1. Spaces prior to a `,` for example https://github.com/ockam-network/ockam/blob/17772ae654d7d86acd5ea3e3e359225c7f93e81d/implementations/rust/ockam/ockam/Cargo.toml#L77 has `version = "0.35.0"...
We use Zeroize for Vault secrets, however there are places (e.g. key agreement) where we have temporary sensitive values, those should use Zeroize [wrappers](https://docs.rs/zeroize/1.4.2/zeroize/#zeroizingz-wrapper-for-zeroizing-arbitrary-values-on-drop) for secure wipe
Metadata
Owner
Metadata
Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.