🆕 Software Suggestion | Mailfence.com #1908

Open
opened 2020-05-12 05:35:14 +00:00 by nitrohorse · 2 comments
nitrohorse commented 2020-05-12 05:35:14 +00:00 (Migrated from github.com)

Basic Information

Name: Mailfence
Category: Email
URL: https://mailfence.com/

Description

Why I am making the suggestion

Based on our research last year, it looks like Mailfence didn't support DNSSEC nor DANE which both are now part of our email criteria. But actually it appears they now support both. Let's double-check if they now fully meet our criteria.

My connection with the software

  • I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
## Basic Information **Name:** Mailfence **Category:** Email **URL:** https://mailfence.com/ ## Description ## Why I am making the suggestion Based on our [research](https://github.com/privacytools/privacytools.io/issues/603#issuecomment-456400331) last year, it looks like Mailfence didn't support DNSSEC nor DANE which both are now part of our [email criteria](https://www.privacytools.io/providers/email/#criteria). But actually it [appears they now support both](https://www.hardenize.com/report/mailfence.com/1589261161). Let's double-check if they now fully meet our criteria. ## My connection with the software <!-- Are you the author? Enthustiastic or early adopter? Friends with the author or requested by them to open the isue? An employee of the software maker? --> - [x] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
ghost commented 2020-05-12 06:08:15 +00:00 (Migrated from github.com)
It has TLS 1.0 enabled. https://www.hardenize.com/report/mailfence.com/1589261161#email_tls https://www.hardenize.com/report/kb.mailfence.com/1589263629#www_tls It depends only on AES. It does not support Chacha 20. https://www.hardenize.com/report/mailfence.com/1589261161#www_tls It does not support Expect CT. https://www.hardenize.com/report/mailfence.com/1589261161#www_expect_ct
dngray commented 2020-05-12 07:03:42 +00:00 (Migrated from github.com)

This is in the https://github.com/privacytools/privacytools.io/tree/pr-add_mailfence branch, the reason it was not added is because they currently do not use any kind of encryption at rest.

From: Daniel Gray

Quick question, do you use any encryption at rest?
I expect that you probably do, but I didn't see anything offically mentioned about it.

From: Mailfence Support

That is presently not the case. We are working on it.

This is in the https://github.com/privacytools/privacytools.io/tree/pr-add_mailfence branch, the reason it was not added is because they currently do not use any kind of encryption at rest. From: Daniel Gray > Quick question, do you use any encryption at rest? > I expect that you probably do, but I didn't see anything offically mentioned about it. From: Mailfence Support > That is presently not the case. We are working on it.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1908
No description provided.