linux-kernel - Re: [PATCH] bug-hunting.rst: Clarify bytes sequence format when making "Code:" human-readable

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: <20180712125711.GB15277@bombadil.infradead.org>
Date:   Thu, 12 Jul 2018 05:57:11 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Kirill Tkhai <ktkhai@...tuozzo.com>
Cc:     corbet@....net, christophe.jaillet@...adoo.fr,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] bug-hunting.rst: Clarify bytes sequence format when
 making "Code:" human-readable

On Thu, Jul 12, 2018 at 11:46:25AM +0300, Kirill Tkhai wrote:
> Bytes have to be separated commas, and this is not obvious
> for a person, who does not write in pure ".byte" assembler.
> Let's clarify this and make visible for people.

Can we delete the entire section and say "run ./scripts/decodecode"
instead?