Added a check to prevent that password protected ssl keys get saved. Thanks to Timo for finding the issue.

Daniel authored Apr 17, 2016 and Daniel committed Apr 17, 2016

---
Daniel Ripoll
I was a DevOps before it was cool.
http://danielripoll.es
+34 6688 27490

Dominik authored Dec 30, 2015 and Dominik committed Dec 30, 2015

After this, it is possible to use both:
 - sub.domain.tld
 - *.domain.tld
together with different folders by rewrite (with rewrite_type = L for sub.domain.tld)
Before it was not clearified which rule matches first, it always dependet on the creation-time of the subdomain

Conflicts:
	server/plugins-available/apache2_plugin.inc.php

- made placeholders visible for apache, too
- added event raise at formdef loading (on_before_formdef and on_after_formdef)
- added possibility to put plugin files into module/lib/plugin.d/ directory

- fixed letsencrypt domain list

- added cron for letsencrypt renewal

https://ssltools.websecurity.symantec.com/checker/views/csrCheck.jsp
You have 1 error
Your CSR contains a challenge phrase.
Adding a challenge phrase to a CSR is not a secure practice. Please generate a new CSR that does not contain a challenge phrase.

The problem occure while buying a cert from https://www.ssls.com/
The support reply with:
"Please regenerate it without the passphrase and try to activate the certificate once again."

- backported patches

- Directive snippets can now be made available to clients; clients can select an available directive snippet for a website - the appropriate snippet will then be written to the vhost configuration file. This is useful for example on nginx where clients have no access to the Options tab of a website.