From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] prevent kernel address space leak via dmesg or /proc files
Date: Mon, 07 Jan 2019 17:21:51 +0000 [thread overview]
Message-ID: <4F57E04C-2DCD-40D5-BCCB-F1710230654D@ipfire.org> (raw)
In-Reply-To: <040e814d-58ea-b456-b4c3-0667c5882601@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
> On 7 Jan 2019, at 17:04, Peter Müller <peter.mueller(a)link38.eu> wrote:
>
> Hello Michael,
>
>
>> Hello,
>>
>> I merged this and edited the release number of the setup package.
> thank you - I am not very sure with handling the release numbers.
> Glad you fixed this for me. :-)
>>
>> For pakfire to recognise changes, the release number (or version number) has to be increased. Since this package does not follow an upstream one, it would have been only the release. I did that for you.
>>
>> Why did we say again this should live in the setup package and not the kernel?
> As far as I can recall, we did not. However, this patch contains
> sysctl parameters, so I guess it makes sens to include them in
> the sysctl package. Kernel flags, for example, will be patched in
> the kernel package.
To be honest, I do not have a better place where this could live.
However, these flags are closely tied to the kernel, so the kernel package would make sense. However, multiple of those can be installed at the same time and loading incompatible settings might happen.
We will leave this for now until we have a better idea.
Best,
-Michael
>
> Thanks, and best regards,
> Peter Müller
>>
>> -Michael
>> --
> Microsoft DNS service terminates abnormally when it recieves a response
> to a DNS query that was never made. Fix Information: Run your DNS
> service on a different platform.
> -- bugtraq
prev parent reply other threads:[~2019-01-07 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 17:05 Peter Müller
2019-01-03 18:08 ` Michael Tremer
2019-01-07 17:04 ` Peter Müller
2019-01-07 17:21 ` 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=4F57E04C-2DCD-40D5-BCCB-F1710230654D@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