public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patches ready for merging
Date: Sun, 09 Sep 2018 17:49:08 +0100	[thread overview]
Message-ID: <35a1442f42a7fcf7fcb194be3d0d73e15cf244ab.camel@ipfire.org> (raw)
In-Reply-To: <bd8f7a97-fcbd-aa28-cfbc-95cf972599b1@link38.eu>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

On Mon, 2018-09-03 at 16:03 +0200, Peter Müller wrote:
> Hello,
> 
> could somebody please have a look at these patches:
> 
> Hardening Unbound default values:
> - https://patchwork.ipfire.org/patch/1907/
> - https://patchwork.ipfire.org/patch/1908/
> - https://patchwork.ipfire.org/patch/1909/

This patchset won't apply.

> Hide kernel address space from privileged users:
> - https://patchwork.ipfire.org/patch/1889/
> 
> Fix background image on URL filter blockpages:
> - https://patchwork.ipfire.org/patch/1904/

The rest is merged now.

> In the past, I made much noise on the list, which I want to apologise
> for here (and hopefully become better in future). If there is nothing
> against it, I would like to see this changes in Core Update 124.
> 
> SSH (client and server) hardening is another topic, which I will
> provide final patches within the next days.
> 
> Thanks for the patience, and best regards,
> Peter Müller


      reply	other threads:[~2018-09-09 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 14:03 Peter Müller
2018-09-09 16:49 ` Michael Tremer [this message]

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=35a1442f42a7fcf7fcb194be3d0d73e15cf244ab.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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