The whole process takes about 15 seconds:
1 The receiver runs secret_share and it generates a one-time public key they can send to the sender
2 The sender runs secret_share, pastes in the public key from the receiver, types the secret, and gets an encrypted response they can send back
3 The receiver pastes in the encrypted response and sees the secret
There are no servers. It’s using very standard/boring/secure crypto (RSA-OAEP and AES-GCM). The private key is never written to disk and is evicted from memory as soon as the payload is decoded (new keys every time). It’s user friendly for a CLI (clear messages, clipboard integration). You can use any chat tool as the communication channel never sees the private key. The only dependencies are Google maintained go packages (term and sys).
Inspired by another project I saw in here 2 days ago, but answering the questions: does this really need a server when we can just use public keys? Can we minimize the codebase and dependencies?