lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 23 Feb 2022 19:00:30 -0600 From: "Gustavo A. R. Silva" <gustavoars@...nel.org> To: Kees Cook <keescook@...omium.org> Cc: Jonathan Corbet <corbet@....net>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Stefano Zacchiroli <zack@...ilon.cc>, Steven Rostedt <rostedt@...dmis.org>, Laura Abbott <labbott@...nel.org>, Julia Lawall <julia.lawall@...ia.fr>, Wenwen Wang <wenwen@...uga.edu>, Thorsten Leemhuis <linux@...mhuis.info>, linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH] Documentation/process: Add Researcher Guidelines On Wed, Feb 23, 2022 at 04:14:03PM -0800, Kees Cook wrote: > As a follow-up to the UMN incident[1], the TAB took the responsibility > to document Researcher Guidelines so there would be a common place to > point for describing our expectations as a developer community. > > Document best practices researchers should follow to participate > successfully with the Linux developer community. > > [1] https://lore.kernel.org/lkml/202105051005.49BFABCE@keescook/ > > Co-developed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> > Co-developed-by: Jonathan Corbet <corbet@....net> > Signed-off-by: Jonathan Corbet <corbet@....net> > Co-developed-by: Stefano Zacchiroli <zack@...ilon.cc> > Signed-off-by: Stefano Zacchiroli <zack@...ilon.cc> > Co-developed-by: Steven Rostedt <rostedt@...dmis.org> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org> > Acked-by: Steve Rostedt <rostedt@...dmis.org> > Acked-by: Laura Abbott <labbott@...nel.org> > Reviewed-by: Julia Lawall <julia.lawall@...ia.fr> > Reviewed-by: Wenwen Wang <wenwen@...uga.edu> > Signed-off-by: Kees Cook <keescook@...omium.org> Acked-by: Gustavo A. R. Silva <gustavoars@...nel.org> See a comment below... > --- > Documentation/admin-guide/index.rst | 1 + > .../admin-guide/researcher-guidelines.rst | 141 ++++++++++++++++++ > 2 files changed, 142 insertions(+) > create mode 100644 Documentation/admin-guide/researcher-guidelines.rst [..] > +* What is the specific problem that has been found? > +* How could the problem be reached on a running system? > +* What effect would encountering the problem have on the system? > +* How was the problem found? Specifically include details about any > + testing, static or dynamic analysis programs, and any other tools or > + methods used to perform the work. > +* Which version of Linux was the problem was found on? Using the most I think there is an extra "was" in the question above. Thanks -- Gustavo
Powered by blists - more mailing lists