From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: [PATCH v2 3/3] generate ECDSA certificate and key on existing installations
Date: Wed, 04 Oct 2017 21:38:20 +0200 [thread overview]
Message-ID: <20171004213820.125b7aae.peter.mueller@link38.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
Generate ECDSA certificate and key file on existing installations
via the update.sh script.
This is required since Apache crashes if some Certificate(Key)File
directives point to non-existing files:
Restarting Apache daemon...
Syntax error on line 17 of /etc/httpd/conf/vhosts.d/ipfire-interface-ssl.conf:
SSLCertificateFile: file '/etc/httpd/server-ecdsa.crt' does not exist or is empty
Key generation only takes a few seconds even on legacy systems. Also
existing installations will then use ECDSA/RSA certificate dual-stack.
Changes from v1: Use the httpscert script (never repeat yourself) and restart
Apache afterwards to load the changes.
Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
---
diff --git a/config/rootfiles/core/115/update.sh b/config/rootfiles/core/115/update.sh
index e0ee121ce..afeeca14a 100644
--- a/config/rootfiles/core/115/update.sh
+++ b/config/rootfiles/core/115/update.sh
@@ -35,6 +35,7 @@ done
openvpnctrl -k
openvpnctrl -kn2n
+
# Extract files
extract_files
@@ -44,10 +45,13 @@ ldconfig
# Update Language cache
#/usr/local/bin/update-lang-cache
+# generate ECDSA certificate and key file to prevent Apache from crashing on existing installations
+/usr/local/bin/httpscert
+
# Start services
openvpnctrl -s
openvpnctrl -sn2n
-
+/etc/init.d/apache restart
# This update need a reboot...
#touch /var/run/need_reboot
reply other threads:[~2017-10-04 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171004213820.125b7aae.peter.mueller@link38.eu \
--to=peter.mueller@link38.eu \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox