linux-kernel - Re: 463 kernel developers missing!

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, 28 Jul 2008 22:01:06 -0400
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Al Viro" <viro@...iv.linux.org.uk>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 463 kernel developers missing!

On 7/28/08, Al Viro <viro@...iv.linux.org.uk> wrote:
> On Mon, Jul 28, 2008 at 09:25:39PM -0400, Jon Smirl wrote:
>  > On 7/28/08, Al Viro <viro@...iv.linux.org.uk> wrote:
>  > > On Mon, Jul 28, 2008 at 03:00:13PM -0400, Jon Smirl wrote:
>  > >
>  > >
>  > > > Other people aren't perfect, I've found over 1,000 typos in the those
>  > >  > names and emails. We need a validation mechanism.
>  > >
>  > > Who's "we", luser, and why would I possibly give a damn for your needs?
>  >
>  > Let's drop the whole Sign-off-by mechanism. If we can't be bothered to
>  > clean up the junk in Signed-off-by why should we bother recording
>  > them? Sign every patch Mickey Mouse, it has the same effect.
>
> That still doesn't answer either of my questions.  As for your question, the
>  point is to have them good enough to make an individual changeset feasible
>  to track.

The file lets you convert the mess that exists in the log file xx-by:
fields back into something reasonable. The messed up email addresses
are verbatim extracted from the log. There is one entry in the file
for each email address that appears in the log. The real names have
been fixed by script and hand to correspond a real name with the
extracted emails.

Now we will differ on the definition of feasible and whether we should
work to prevent more messed up emails/names from getting into the log.
That's the central question here, how much are you allowed to
obfuscate (on purpose or accidentally) your identity in an xx-by?

I should also point out that external information (Google) was needed
to identify several hundred names, there was insufficient information
in the log or kernel source. If we have to reconstruct this mapping
ten years from now for some random lawsuit, the external information
may not be there.

-- 
Jon Smirl
jonsmirl@...il.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/