DuckCorp » DuckCorp Infrastructure

h1. Security Model

h2. Status in DuckCorp

h3. DNS

We would prefer not to have to trust the DNS hierarchy, but, it is convenient for most users and alternative systems at the moment did not solve the problem in a satisfactory manner.

Our [[DNS#DNSSEC|zones are secured using DNSSEC]]. Tenants' zones will be signed when handling the KSK rollover with the parent zone is smooth enough (and fully automated, WIP).

h3. PKI

The "DuckCorp CA:https://ca.duckcorp.org/ was created when usage of HTTPS was not very common and certificates very expensive. Time also proved we cannot trust the top CAs and their "broken security model":https://en.wikipedia.org/wiki/Certificate_authority#CA_compromise.

Nowadays it is no more viable to operate a self-signed CAs as all softwares and providers rejects them. Moreover, it is quite inconvenient to setup a custom CA for non-technical users and it makes our life difficult to communicate and exchange with external entities through our infrastructure. That is why we decided to trust "Let's Encrypt":https://letsencrypt.org/ to generate certificates. The root of the problem is not solved but at least the validation process is sound and open. It is also automated, using Free Softwares, so we can handle certificate management by ourselves. We keep using our CA for internal services but public-facing ones now use Let's encrypt (#676).

To counteract the loss in security we use another system (DANE, see below); it requires trusting the DNS hierarchy, but there are less players involved and it has proved more reliable. Unfortunately DANE adoption is quite slow; nevertheless we decided to implement it.

Initially we only used our own CA and published TLSA records for all services. Since we now use Let's Encrypt, TLSA publication has been reworked to play nice together. It is fully automated (compared to renewal with our own CA) but currently not deployed for all services yet (#675).

h2. DNSSEC

See [[DNS#DNSSEC]].

h2. DANE

h3. Introduction

"DANE":https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities is a security protocol used to reinforce TLS certificate validation by publishing certain information in the DNS. It requires your DNS zones to be secured using "DNSSEC":https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions.

h3. Checking DANE

The "danetls":https://github.com/shuque/danetls tool is not packaged but there is a web service called "danecheck":https://www.huque.com/bin/danecheck by the same author.

h3. DANE adoption

These are just notes to check on DANE adoption in various client software.

* HTTPS: "plugins for majors browsers were developed and abandoned":https://www.dnssec-validator.cz/ because necessary API support in the browsers vanished and there is no replacement

* SMTP: seems to have gained traction, suggested by the various checkers, Postfix supports it and we support it (see [[Mail]])

* IMAP/POP3: "Thunderbird integration was refused":https://bugzilla.mozilla.org/show_bug.cgi?id=1479423 because it needs to be integrated in Firefox core first, but the "Firefox integration":https://bugzilla.mozilla.org/show_bug.cgi?id=672600 does not seem to go anywhere

* IRC: "Weechat integration":https://github.com/weechat/weechat/pull/121 is not making much progress despite a patch being available

* XMPP-c2s: ???

* XMPP-s2s: Prodosy has an "experimental module":https://modules.prosody.im/mod_s2s_auth_dane.html but it is unmaintained and supposed to crash sometimes (according to the known issues)