1. 24 3月, 2018 2 次提交
  2. 21 3月, 2018 11 次提交
  3. 10 3月, 2018 1 次提交
    • D
      docs: clarify security-bugs disclosure policy · 7f5d465f
      Dave Hansen 提交于
      I think we need to soften the language a bit.  It might scare folks
      off, especially the:
      
      	 We prefer to fully disclose the bug as soon as possible.
      
      which is not really the case.  Linus says:
      
      	It's not full disclosure, it's not coordinated disclosure,
      	and it's not "no disclosure".  It's more like just "timely
      	open fixes".
      
      I changed a bit of the wording in here, but mostly to remove the word
      "disclosure" since it seems to mean very specific things to people
      that we do not mean here.
      Signed-off-by: NDave Hansen <dave.hansen@linux.intel.com>
      Reviewed-by: NDan Williams <dan.j.williams@intel.com>
      Reviewed-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Acked-by: NKees Cook <keescook@chromium.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
      Cc: Andrea Arcangeli <aarcange@redhat.com>
      Cc: Andy Lutomirski <luto@kernel.org>
      Cc: Tim Chen <tim.c.chen@linux.intel.com>
      Cc: Alexander Viro <viro@zeniv.linux.org.uk>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      7f5d465f
  4. 08 3月, 2018 21 次提交
  5. 23 2月, 2018 5 次提交