So last step is to propagate the change to Eglide restarting the minion.

I prepared such a change Wednesday, and committed now, as @tomjerr confirmed the key is working fine (per your manual add).

The more immediate and interesting question: should we drop TLS 1.0?

The TLS imirhil report evaluates what they consider as the best practices.

3. refactoring done.
4. filtering partially done: only failure are reported, Jenkins notifies, we consume.
5. to automate without human assertion system status isn't currently considered as valuable

Redirect to SSL web server configuration

nasqueron-devcentral transferred

/etc/postfix/main.cf setting has been switched back to smtpd_tls_security_level = may, mail server restarted.

Done this night for both.

I've checked the current state of the migration. We only have two certificates remaining and we're done:

Current status

Currently, configuration file contains the following instructions:

In T853#9085, @dereckson wrote:

We need a script to automate the process.

5.6.26 is a security release according the changelog.

Step 4 done for B to D, but currently every failure will be reported. And we don't exploit in the artefact log what's failing.

Superseded by T846.

No issue ownCloud related: the Let's encrypt location block was in 80 server block, not in 443 one.

A deny rule blocked all the URL starting by a . to protect .htpasswd files.

@amj do you remmeber anything still do do here?

3A alternative: a cron job running the command for us and generating a report published somewhere Jenkins has access to.