ockam
ockam copied to clipboard
Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.
This commit (potentially) fixes #3105. Because the router run-loop does not own the Router, it is not dropped after the loop terminates. Note: the commit isn't signed because I forgot...
add/list/delete project enrollers from the (internal) project authority. @adrianbenavides I think you can take over from here and reorganize the code or cli interface if needed.
Here's an example run https://github.com/build-trust/ockam/actions/runs/2822798599
Trying to startup different nodes, with _different_ identities. Guess the way to go now is to start the nodes with `--skip-defaults` and then create the vault, the identitiy and then...
Add an abstraction layer on top of `connect_to` to make it easier to write commands' api req/res handlers. It removes a lot of boilerplate around calling the background node and...
``` > ockam tcp-inlet delete --node --force(optional) > ockam tcp-outlet delete --node --force(optional) > ockam tcp-inlet show > ockam tcp-outlet show > ockam tcp-inlet list --node > ockam tcp-outlet list...
Fix #3145 Fix #3146 IMO, this should work but it doesn't. Here is how I think `ockam tcp-connection list --node n1` works 1. Calls `list_connections` 2. `api::list_tcp_connections()` create a RequestBuilder...
We currently have: ``` ockam portal create tcp-inlet .. ockam portal create tcp-outlet ... ``` We want to change these to: ``` ockam tcp-inlet create ... ockam tcp-outlet create ......
## Current Behaviour ``` > ockam tcp-listener create error: The following required arguments were not provided: USAGE: ockam tcp-connection create [OPTIONS] For more information try --help ``` ## Should Be...
## Current Behaviour ``` > ockam node wrong error: Found argument 'wrong' which wasn't expected, or isn't valid in this context USAGE: ockam node [OPTIONS] For more information try --help...