linux-kernel - Re: Tracking and crediting bug reporters

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 May 2008 13:52:22 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	alan@...rguk.ukuu.org.uk
Cc:	corbet@....net, linux-kernel@...r.kernel.org
Subject: Re: Tracking and crediting bug reporters

From: Alan Cox <alan@...rguk.ukuu.org.uk>
Date: Mon, 12 May 2008 19:20:19 +0100

> > If the rest of the community is agreeable, it would be nice to make an
> > immediate start on this; it's not yet too late to get reasonable data for
> > the 2.6.26 kernel, and to have the habits well ingrained for 2.6.27.
> > 
> > Thoughts?
> 
> I cannot add a tag with a third party personal information upon it
> without their permission nor can anyone else in a part of the world with
> any vaguely resembling privacy laws. So we need to document that it is
> added with permission of the reporter only.

This is why I personally do not accept private bug reports or kernel
questions, I always direct them to post to the appropriate public
mailing list and CC: me if appropriate.

That solves the whole "privacy" issue quite neatly.
--
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/