Hi all,
Thank you (especially Willy) for your effort on this.
Out of the 3 paragraphs, the first one looks good to me as-is, but for
the last two I propose the slightly edited versions below.
On Sat, Oct 07, 2023 at 04:04:54PM +0200, Willy Tarreau wrote:
> +Please note that the respective polici
rstand those policies as they differ from
> > > > secur...@kernel.org's policy.
> > > >
> > > > Suggested-by: Solar Designer
> > > > Signed-off-by: Sasha Levin
> > >
> > > Sorry, but NACK, see below...
I like Sasha's PATCH v2 better, but if Kee
nux-distros list policy and clarify that the reporter
> > must read and understand those policies as they differ from
> > secur...@kernel.org's policy.
> >
> > Suggested-by: Solar Designer
> > Signed-off-by: Sasha Levin
> > ---
> >
> > Cha
;
> >>> Second, clarify that the reported must provide a tentative public
> >>> disclosure date and time in his first contact with linux-distros.
> >>>
> >>> Suggested-by: Solar Designer
> >>> Signed-off-by: Sasha Levin
> >>> --
> >>> On Mon, May 22, 2017 at 2:08 PM, Solar Designer
> >>> wrote:
> >>> > On Mon, May 22, 2017 at 01:57:03PM +0200, Djalal Harouni wrote:
> >>> >> *) When modules_autoload_mode is set to (2), automatic module loading
> >>
On Mon, May 22, 2017 at 03:49:15PM +0200, Djalal Harouni wrote:
> On Mon, May 22, 2017 at 2:08 PM, Solar Designer wrote:
> > On Mon, May 22, 2017 at 01:57:03PM +0200, Djalal Harouni wrote:
> >> *) When modules_autoload_mode is set to (2), automatic module loading is
> >
Hi Djalal,
Thank you for your work on this!
On Mon, May 22, 2017 at 01:57:03PM +0200, Djalal Harouni wrote:
> *) When modules_autoload_mode is set to (2), automatic module loading is
> disabled for all. Once set, this value can not be changed.
What purpose does this securelevel-like property ("O
