public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 5d673af27fc2105b72af6bef16a68de333aa0fa7
Date: Wed, 06 May 2020 10:25:31 +0000	[thread overview]
Message-ID: <49HCQz5l4Fz2xdZ@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2054 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 3.x development tree".

The branch, master has been updated
       via  5d673af27fc2105b72af6bef16a68de333aa0fa7 (commit)
      from  4c46148399f0920f72efe2a5f70a0e2f591e3042 (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 5d673af27fc2105b72af6bef16a68de333aa0fa7
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Tue May 5 22:19:36 2020 +0200

    sysctl.conf: Turn on hard- and symlink protection
    
    This backports 29a8992b7228771fb2cfc68679596598fb01105a into IPFire 3.x
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:
 setup/setup.nm                     | 2 +-
 setup/sysctl/kernel-hardening.conf | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

Difference in files:
diff --git a/setup/setup.nm b/setup/setup.nm
index 09d94e23d..cc8454bfa 100644
--- a/setup/setup.nm
+++ b/setup/setup.nm
@@ -5,7 +5,7 @@
 
 name       = setup
 version    = 3.0
-release    = 14
+release    = 15
 arch       = noarch
 
 groups     = Base Build System/Base
diff --git a/setup/sysctl/kernel-hardening.conf b/setup/sysctl/kernel-hardening.conf
index 33e096c7c..d92485d61 100644
--- a/setup/sysctl/kernel-hardening.conf
+++ b/setup/sysctl/kernel-hardening.conf
@@ -7,3 +7,7 @@ kernel.dmesg_restrict = 1
 # Improve KASLR effectiveness for mmap.
 vm.mmap_rnd_bits = 32
 vm.mmap_rnd_compat_bits = 16
+
+# Turn on hard- and symlink protection
+fs.protected_symlinks = 1
+fs.protected_hardlinks = 1


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

                 reply	other threads:[~2020-05-06 10:25 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=49HCQz5l4Fz2xdZ@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