MAILFENCE AT THE RIGHTSCON BRUSSELS 2017
Mailfence at RightsCon Brussels – 2017 received a warm welcome from journalists, activists, bloggers and other privacy-conscious conference attendees. We met impressive individuals from a multitude of sectors: cybersecurity, healthcare, education and human rights, to name just a few. They all share the same spirit and feeling that privacy-respecting digital solutions are needed to regain digital privacy and freedom.
Mailfence Demo Session Presentation:
We presented a sample session of our secure and private email service , where we briefly presented the following points:
Why we need to protect data
Why email data?
What secure email technologies are available, and which ones are suitable?
The complexity of “true” end-to-end list of australia whatsapp phone numbers encryption
Why is it important to make “true” end-to-end encryption easy to use?
Introducing the unique aspects of Mailfence:
Advanced Key Management
Integrated keystore (independent of any plugin/add-on)
“True” end-to-end encryption based on OpenPGP (supports inline and PGP/ MIME formats )
Digital signatures
All this in a very nice and easy to use interface.
The entire presentation can be found here .
A short hands-on demonstration was given at that point, covering key escrow and email encryption and decryption. Finally, we concluded our presentation with the unique advantages of Mailfence over all other secure email solutions:
Users have full control over the management of their keys
Full Reversibility – Users can export their encrypted key pair and other public keys along with their encrypted data.
Complete freedom and no “digital islands” : Users can send plaintext emails, digitally signed plaintext emails, signed emails and end-to-end encrypted emails (to any other PGP-compatible solution, with full interoperability).
We conclude the sample session with a Q&A session:
Q1: What happens when a user forgets the passphrase for their private key?
There is nothing we can do. The user has to upload his revocation certificate to the public key servers (in case he has published his public key) to inform others that he is no longer using it. In case a user has not published his public key on the public key servers, he can send a signed email with his new public key as an attachment to all recipients, and ask them to use this new public key to send him encrypted messages in the future .