From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, seventeen, updated. 851fba0e8df26b85c39760d0e8307ec3b6abdc46
Date: Wed, 05 Nov 2014 22:12:00 +0100 [thread overview]
Message-ID: <20141105211200.2E67121261@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, seventeen has been updated
via 851fba0e8df26b85c39760d0e8307ec3b6abdc46 (commit)
from 3e1145e1a0b1a08bf61d6c4962eeae48e3d0c355 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 851fba0e8df26b85c39760d0e8307ec3b6abdc46
Author: Timmothy Wilson <phouthio(a)wegwerfemail.de>
Date: Wed Nov 5 22:08:02 2014 +0100
httpscert: Create certificate with SHA256 hash
-----------------------------------------------------------------------
Summary of changes:
src/scripts/httpscert | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/src/scripts/httpscert b/src/scripts/httpscert
index d0e23fa..e20f789 100644
--- a/src/scripts/httpscert
+++ b/src/scripts/httpscert
@@ -14,7 +14,7 @@ case "$1" in
/bin/cat /etc/certparams | sed "s/HOSTNAME/`hostname -f`/" | /usr/bin/openssl \
req -new -key /etc/httpd/server.key -out /etc/httpd/server.csr
echo "Signing certificate"
- /usr/bin/openssl x509 -req -days 999999 -in \
+ /usr/bin/openssl x509 -req -days 999999 -sha256 -in \
/etc/httpd/server.csr -signkey /etc/httpd/server.key -out \
/etc/httpd/server.crt
;;
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-11-05 21:12 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=20141105211200.2E67121261@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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