Mesince Forum


Lesson 2 -- How Public Keys Exchanged
Read 147 times
* August 31, 2018, 01:25:23 AM
The previous lesson is about the idea in the designing of the logo and service mark and their pronunciation. Let’s learn more about public key exchange today.
This is another very important function of MeSince. For example, when someone sends an encrypted email to his friend, given that he has his friend's public key in hand, the public key will be uploaded to MeSince Certificate Database (CerDB), and after that, if another person wants to send encrypted email to the friend, MeSince will automatically encrypt the email using the public key stored in the MeSince Certificate Database (CerDB). In the whole process, the friend does not have any of our certificates. The certificate (public key) used to encrypt email being sent to him, belongs to him. In a word, this function does not require a user to have used MeSince before.
If you send email to someone who does not have any certificate at all, in other words, our MeSince Certificate Database (CerDB) does not contain any of his certificates,MeSince will issue a key pair and a self-signed certificate, and use this certificate to send the encrypted email to him. MeSince will also send him a plain text email under your name, to show him how to install MeSince or to download the certificate issued to him to decrypt the email you have sent.
In addition, we support encryption using multiple certificates. We will use every certificate under one email address to encrypt an email, so that a recipient can decipher an encrypted email using any of his certificates.
« Last Edit: October 29, 2018, 06:19:57 AM by v-danny »