public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 6094f35b5aea86b80e761302f83dc8c09a52b63b
Date: Fri, 19 Jan 2024 06:11:32 +0000	[thread overview]
Message-ID: <4TGTlS63cvz2xjP@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2316 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, next has been updated
       via  6094f35b5aea86b80e761302f83dc8c09a52b63b (commit)
      from  36c16c71ed854b5bc43b79be926dd1d00f9091ff (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 6094f35b5aea86b80e761302f83dc8c09a52b63b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Jan 19 06:10:26 2024 +0000

    core183: generate new rsa before apache start
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/core/183/update.sh | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

Difference in files:
diff --git a/config/rootfiles/core/183/update.sh b/config/rootfiles/core/183/update.sh
index 5930ad324..51483bb7d 100644
--- a/config/rootfiles/core/183/update.sh
+++ b/config/rootfiles/core/183/update.sh
@@ -119,15 +119,6 @@ ldconfig
 chmod -v 750 /etc/sudoers.d
 chmod -v 640 /etc/sudoers.d/*
 
-# Start services
-/etc/rc.d/init.d/apache start
-if grep -q "ENABLE_SSH=on" /var/ipfire/remote/settings; then
-	/etc/init.d/sshd start
-fi
-if grep -q "ENABLED=on" /var/ipfire/vpn/settings; then
-	/etc/rc.d/init.d/ipsec start
-fi
-
 # Check apache rsa key and replace if it is too small
 KEYSIZE=$(openssl rsa -in /etc/httpd/server.key -text -noout | sed -n 's/Private-Key:\ (\(.*\)\ bit.*/\1/p')
 if [ $KEYSIZE \< 2048 ]; then
@@ -143,6 +134,16 @@ if [ $KEYSIZE \< 2048 ]; then
 		-out /etc/httpd/server.crt &>/dev/null
 fi
 
+# Start services
+/etc/rc.d/init.d/apache start
+if grep -q "ENABLE_SSH=on" /var/ipfire/remote/settings; then
+	/etc/init.d/sshd start
+fi
+if grep -q "ENABLED=on" /var/ipfire/vpn/settings; then
+	/etc/rc.d/init.d/ipsec start
+fi
+
+
 # Rebuild initial ramdisks
 dracut --regenerate-all --force
 KVER="xxxKVERxxx"


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2024-01-19  6:11 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=4TGTlS63cvz2xjP@people01.haj.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