From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 96737543858a2d78d61da981dd10c5e9a3b671a4
Date: Mon, 13 Apr 2015 15:37:59 +0200 [thread overview]
Message-ID: <20150413133800.2AD2D21AD0@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1640 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 96737543858a2d78d61da981dd10c5e9a3b671a4 (commit)
from b171633c7e15a1fceacfae9953ad9b5b6a07e945 (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 96737543858a2d78d61da981dd10c5e9a3b671a4
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Mon Apr 13 15:35:15 2015 +0200
backup: Include sshd config file.
The sshd config file was not included in the backups, so if the port
was switched from the default one to another one, the changed value was
correctly restored and displayed in the WUI but still the original sshd
config file was present and the default port has been used.
This issue is fixed by this commit.
Fixes #10446.
-----------------------------------------------------------------------
Summary of changes:
config/backup/include | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/backup/include b/config/backup/include
index d7a1d3a..159ff9a 100644
--- a/config/backup/include
+++ b/config/backup/include
@@ -13,6 +13,7 @@
/etc/hosts*
/etc/httpd/*
/etc/ssh/ssh_host*
+/etc/ssh/sshd_config
/etc/logrotate.d
/var/ipfire/auth/users
/var/ipfire/dhcp/*
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-04-13 13:37 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=20150413133800.2AD2D21AD0@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