Hello You will not see that public key only information for users in the webfrontend. You only can see that certificate info, if that person has uploaded its complete certificate into SOGo. But it works with others too, even with people without SOGo account.
Is that user using PGP signed E-Mails? That will never work, as S/MIME and PGP are completely different. Is the certificate of the sender valid? I had once a customer trying to send emails with a certificate no longer valid for 2 months. Kind regards, Christian Mack Am 15.05.20 um 12:32 schrieb "Ndanga brice" (ndangabr...@gmail.com): > Hello Christian Mack, > > I have followed the below procedure that permit to upload certificate for > signing and encrypting message. > That procedure work fine we some users and we have been able to sign and > encrypt message. > > But unfortunately with some users, when you receiving first signing message, > click on that message and go the check in address book in order to be sure > that the cerficate has been uploaded, you notice that there isn't information > to let you know if the certificate has been successful uploaded > > We have tried to re-sent signing message and check again, but nothing. > > Can you tell me what can be the problem ? > > thank in advance. > > -----Message d'origine----- > De : users-requ...@sogo.nu [mailto:users-requ...@sogo.nu] De la part de > Christian Mack > Envoyé : mercredi 13 mai 2020 15:20 > À : users@sogo.nu > Objet : Re: [SOGo] Cannot send encrypt message to users > > Hello > > Am 13.05.20 um 09:28 schrieb "Ndanga brice" (ndangabr...@gmail.com): >> Hello >> >> I have imported my certificate with pkcs12 format in sogo and send signed >> message to user. >> But when I try to send encrypted message to that user, it's failed. >> > > You do not understand asymmetric crypto then :-) > > Beware, this explanation is heavily simplified. > > Symmetric crypto means, you have one key for encrypting and the same key > for decrypting. > Problem with that is, that you have to exchange the key securely from > the sender to the recipient. > If anybody except your intended recipient gets that key, you are screwed. > > A S/MIME certificate consists of 2 keys. > A private key and a corresponding public key. > Corresponding means here, that everything you encrypt with one of them, > you can only decrypt with the other one. > Because of that it is called asymmetric crypto. > > The public key can be given to everyone, not just your intended recipient. > Security is guaranteed by the fact, that the owner of a certificate is > the only one knowing the secret key. > > When you cryptographically sign a message, you use your private key for > doing so. > With that everyone can check that signature by using your public key. > As only you have access to that private key, only you can make that > particular signature matching that message content. > That is the proof for others, that this email is from you, and nobody > tampered with the content. > > When encrypting a message, you want to be sure, that only your intended > recipient can read that message. > Therefore you use the public key of your recipient to encrypt that message. > Now only the owner of the corresponding private key can decrypt and read > that message. > >> Please could you tell me the procedure to send encrypted message to user ? >> > > What you uploaded into SOGo is YOUR certificate. > But as I explained above, you need the public keys of all RECIPIENTS of > that email for encryption. > > 1) All intended recipients of an encrypted email have to send you a > S/MIME signed email first. > With that they also send you their public key. > 2) All intended recipients have to be in your personal address book in SOGo. > 3) Read that signed emails in SOGo Webfrontend at least once. > Now SOGo will store those public keys for the corresonding email address > in your personal address book for you. > 4) From then on you can send them encrypted emails. > > > Kind regards, > Christian Mack > -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
