Oleksandr Deundiak

Mitigate code duplication in WebSocket and Tcp transports

4

Mitigate code duplication in WebSocket and Tcp transports. For example TcpRouter and WebSocketRouter are identical, except log messages and return errors. Let's consider moving essential parts of Transport implementations to...

Create custom async Clone trait

13

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...

Stop deriving Message trait implementation for all Serialize&Deserialize structs

1

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)

Switch to using Handle everywhere we interact with Workers

1

[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

Switch to using rng from vault where it's possible

2

Should be done after #1845

Replace TCP port 5000 in examples&guides

4

Latests MacOS release uses port 5000 for some service, therefore guides that use that port won't work

Use Zeroize for temporary sensitive data

8

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