You will need to establish a shared secret in person in advanced or over a trusted channel out of band.

You can configure your preferred cipher in the menu. Currently aesgcm is not included because it will require additional packages. `openssl enc’ is not compatible with aesgcm due to to complexities in handling the authentication tag. I do plan on integrating this in the future however.

I think It’s important to note this later of encryption is completely redundant with Tor integration. We are already e2ee encrypted with without openssl encryption. I just saw no reason not to include it as overhead is minimal.

I haven’t tried to break that yet, but I should find out the limits. I have sent pretty lengthy payloads while on 6kbs encoding quality with no issues. I know we can send aleast 60 second

With some work we should theoretically be able to configure any networking pipe. I like Tor for it’s large distributed userbase/built in plug and play circumship transports and reliability is the short answer. It passes simple text encoded audio which should make it really easy to plug n play other networks. Also, I’m using open SSL as an additional encryption layer, it should be possible to configure any other encryption primatives you want easily. It doesn’t have to use this library. It’s just the one I chose.

I have been tinkering with this as well. There is a really broad application to this if you know how to develop websites.

Simplex does check alot of those boxes… but smp traffic is easily identifiable unless your jumping through the major hoops of establishing a totally anonymous proxy.

An encoded message on a pastebin through tor. Congratulations, you’ve entered pedophile/terrorist level security realm.

Thats to bad being anonymous and secure puts you in that category. It shouldn’t!