public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f62b488f82b5eb6bbbc1b57d90a919d61346ef5f
Date: Mon, 20 Jun 2022 20:12:59 +0000	[thread overview]
Message-ID: <4LRgn81nJPz2y51@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2993 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  f62b488f82b5eb6bbbc1b57d90a919d61346ef5f (commit)
       via  2c38893da43383ffb57022575fa56a255b012a93 (commit)
       via  2bbfa1b72c32712997183e4813f813d443a48d81 (commit)
      from  1452738c2e22562d84a7c6af683a2f9bce88fd55 (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 f62b488f82b5eb6bbbc1b57d90a919d61346ef5f
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Mon Jun 20 20:10:47 2022 +0000

    sysctl: Actually arm YAMA
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

commit 2c38893da43383ffb57022575fa56a255b012a93
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Mon Jun 20 19:50:16 2022 +0000

    Core Update 169: Ship keyutils
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

commit 2bbfa1b72c32712997183e4813f813d443a48d81
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Mon Jun 20 19:48:55 2022 +0000

    Core Update 169: Ship poppler
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

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

Summary of changes:
 config/etc/sysctl.conf                                        | 3 +++
 config/rootfiles/{oldcore/125 => core/169}/filelists/keyutils | 0
 config/rootfiles/{oldcore/110 => core/169}/filelists/poppler  | 0
 3 files changed, 3 insertions(+)
 copy config/rootfiles/{oldcore/125 => core/169}/filelists/keyutils (100%)
 copy config/rootfiles/{oldcore/110 => core/169}/filelists/poppler (100%)

Difference in files:
diff --git a/config/etc/sysctl.conf b/config/etc/sysctl.conf
index 6bf3bc887..4d4f765ea 100644
--- a/config/etc/sysctl.conf
+++ b/config/etc/sysctl.conf
@@ -108,3 +108,6 @@ kernel.core_uses_pid = 1
 
 # Block non-uid-0 profiling
 kernel.perf_event_paranoid = 3
+
+# Deny any ptrace use as there is no legitimate use-case for it on IPFire
+kernel.yama.ptrace_scope = 3
diff --git a/config/rootfiles/core/169/filelists/keyutils b/config/rootfiles/core/169/filelists/keyutils
new file mode 120000
index 000000000..4311917e5
--- /dev/null
+++ b/config/rootfiles/core/169/filelists/keyutils
@@ -0,0 +1 @@
+../../../common/keyutils
\ No newline at end of file
diff --git a/config/rootfiles/core/169/filelists/poppler b/config/rootfiles/core/169/filelists/poppler
new file mode 120000
index 000000000..39aa6c263
--- /dev/null
+++ b/config/rootfiles/core/169/filelists/poppler
@@ -0,0 +1 @@
+../../../common/poppler
\ No newline at end of file


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

                 reply	other threads:[~2022-06-20 20: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=4LRgn81nJPz2y51@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