With asymmetric encryption there are 2 keys - 1 is public (= everyone can look it up) and 1 is private (only the receiver has that key). Those are mathematically related.
When I send a message, I use the receivers Public key to encrypt the message - so that message is only decryptable with the private key, so the recipient alone can decrypt it.
Varen
joined 1 year ago
Looking forward to it!
That looks exactly how I hoped for ^^ well done, I like it!
It was a matter of get-used-to for me. Having subscriptions and the possibility to either place a thread or just a quick post was for me a feature I didn‘t know I wished for. I just need to look after microblogs the same way I look at threads… and therefore I hope that the implementation in Artemis will be likewise to Threads but still having it split one from another - pretty much how kbin has it on its own already
The private key never leaves the one it belongs to - if it does, then the encryption isn‘t secure anymore. If keys are sent, then the public ones, which are ‚public‘ (e.g. let me send you my public key, so you can send encrypted messages to me).
When you create a key pair, you get which the private and which the public one is. Keep your private key, private and you‘re the only holdener.
For advanced security, the messages (e.g. E-Mails) are secured on top with TLS, which encrypts the message on its way. If there‘s a man-in-the-middle attack, he would just see the encrypted message with no key to decrypt it.