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: [PATCH] disable runtime kernel replacement via kexec
Date: Mon, 20 Aug 2018 10:03:44 +0100	[thread overview]
Message-ID: <8e45ff496b845cea51ed1ba0de53963b1ce2816f.camel@ipfire.org> (raw)
In-Reply-To: <3e6df0d2-7cc8-240c-4d8d-cb154b9fccaa@link38.eu>

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

To avoid this noise on the list, please *thoroughly* test those changes before.

Although this is a trivial patch itself with only a one-line change, those
changes can have loads of implications.

Best,
-Michael

On Sun, 2018-08-19 at 20:14 +0200, Peter Müller wrote:
> Hello,
> 
> please ignore this patch as it contains some errors leading
> to key lookup failures in sysctl.
> 
> Sorry for the inconvenience.
> 
> Thanks, and best regards,
> Peter Müller
> 
> > Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> > ---
> >  config/etc/sysctl.conf | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/config/etc/sysctl.conf b/config/etc/sysctl.conf
> > index 011c4287e..5735dd42e 100644
> > --- a/config/etc/sysctl.conf
> > +++ b/config/etc/sysctl.conf
> > @@ -48,3 +48,7 @@ kernel.kptr_restrict = 1
> >  
> >  # Avoid kernel memory address exposures via dmesg.
> >  kernel.dmesg_restrict = 1
> > +
> > +# Turn off kexec, even if it's built in (dangerous because
> > +# it can replace the running kernel).
> > +kernel.kexec_load_disabled = 1
> > 
> 
> 


  reply	other threads:[~2018-08-20  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 15:31 Peter Müller
2018-08-19 18:14 ` Peter Müller
2018-08-20  9:03   ` Michael Tremer [this message]
2018-08-20 15:17     ` Peter Müller

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=8e45ff496b845cea51ed1ba0de53963b1ce2816f.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