linux-kernel - Re: [PATCH] Documentation/SubmittingPatches: implicit permission for public reports

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 24 Oct 2012 09:40:36 -0500
From:	Ed Cashin <ecashin@...aid.com>
To:	Jonathan Corbet <corbet@....net>
CC:	"rob@...dley.net" <rob@...dley.net>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"dan.carpenter@...cle.com" <dan.carpenter@...cle.com>,
	"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation/SubmittingPatches: implicit permission
 for public reports

On Oct 24, 2012, at 10:36 AM, Jonathan Corbet wrote:

> On Wed, 24 Oct 2012 10:22:02 -0400
> Ed Cashin <ecashin@...aid.com> wrote:
> 
>> +contribution.  Please note that this tag should not be added without
>> +the reporter's permission unless the problem was reported in a public
>> +forum.  That said, if we diligently credit our bug reporters, they
> 
> I know what you're getting at, but this reads as if one should add the tag
> even if it's contrary to the reporter's wishes.  How about something like:
> 
> 	If the bug report was via a private channel, please obtain the
> 	reporter's permission before adding this tag - or, even better,
> 	ask that the report be posted publicly.
> 
> ?

Yes, that's a great improvement, thanks!

-- 
  Ed Cashin
  ecashin@...aid.com


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/