linux-kernel - Re: [PATCH] Fix NUL (\0 or \x00) specification in string

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]

Message-ID: <20150106192804.GL4806@salidar.dom.custoft.eu>
Date:	Tue, 6 Jan 2015 20:28:04 +0100
From:	Giel van Schijndel <me@...tis.eu>
To:	dsterba@...e.cz, linux-kernel@...r.kernel.org,
	Armin Schindler <mac@...ware.de>,
	Karsten Keil <isdn@...ux-pingi.de>,
	"open list:ISDN SUBSYSTEM" <netdev@...r.kernel.org>
Subject: Re: [PATCH] Fix NUL (\0 or \x00) specification in string

On Mon, Jan 05, 2015 at 16:00:26 +0100, David Sterba wrote:
> I'm replying to all your recent patches here as they are fixing things
> reported in http://www.viva64.com/en/b/0299/ . I'ts a good practice to
> give the credit the reporter.
> 
> The blogpost also contains analyses of the issues so it could help
> reviewing the patches.

I guess you suggest I use a 'Reported-(at|by)' line?

Would something like the below suffice? I found similar log entries in the
commit log, e.g. bf3204cb, except that those add an e-mail address for
the reporters, which I don't think is necessary in this case.
> Reported-at: http://www.viva64.com/en/b/0299/
> Reported-by: Andrey Karpov
> Reported-by: Svyatoslav Razmyslov

-- 
Met vriendelijke groet,
With kind regards,
Giel van Schijndel
--
The #1 programmer excuse for legitimately slacking off:
 "My code's compiling."
  -- http://xkcd.com/303/

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)