From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 42e48984ad94fba114cde99a31efde63f2f42101
Date: Sun, 24 Feb 2019 09:57:42 +0000 [thread overview]
Message-ID: <20190224095742.570CE84FDD4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1547 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 42e48984ad94fba114cde99a31efde63f2f42101 (commit)
from c09758302b419c13246f41b9b0be9dfe1e0b1d14 (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 42e48984ad94fba114cde99a31efde63f2f42101
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Feb 24 10:55:49 2019 +0100
core128: apply local sshd config
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/128/update.sh | 3 +++
1 file changed, 3 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/128/update.sh b/config/rootfiles/core/128/update.sh
index 9c9486e41..b6366144b 100644
--- a/config/rootfiles/core/128/update.sh
+++ b/config/rootfiles/core/128/update.sh
@@ -104,6 +104,9 @@ ldconfig
# Reload sysctl.conf
sysctl -p
+# Apply local configuration to sshd_config
+/usr/local/bin/sshctrl
+
# Start services
if grep -q "ENABLED=on" /var/ipfire/vpn/settings; then
/etc/init.d/ipsec restart
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-02-24 9:57 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=20190224095742.570CE84FDD4@people01.i.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