linux-kernel - Re: [PATCH v4 0/2] Recommend denylist/allowlist instead of blacklist/whitelist

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, 15 Jun 2020 06:21:43 +0200
From:   Jiri Slaby <jslaby@...e.cz>
To:     Pavel Machek <pavel@....cz>, Michael Ellerman <mpe@...erman.id.au>
Cc:     SeongJae Park <sjpark@...zon.com>, Joe Perches <joe@...ches.com>,
        akpm@...ux-foundation.org, apw@...onical.com,
        SeongJae Park <sjpark@...zon.de>, colin.king@...onical.com,
        sj38.park@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/2] Recommend denylist/allowlist instead of
 blacklist/whitelist

On 14. 06. 20, 23:29, Pavel Machek wrote:
>> I agree you have to draw the line somewhere, there will always be
>> someone somewhere that's offended by something. But this seems like a
>> pretty easy case.

Yes, hence I left up to the minority and/or the touched culture.

>> It's not like blacklist / whitelist are even good to begin with, it's
>> not obvious which is which, you have to learn that black is bad and
>> white is good.
>>
>> Blocklist (or denylist?) and allowlist are actually more descriptive and
>> less likely to cause confusion.
> 
> You do not understand how word "blacklist" is used inside the kernel,
> do you? Do a quick grep.

And now, do the same for "blocklist".

And is "denylist" a proper word? As grep gives zarro results...

It's not that easy to find alternatives. OTOH, admittedly, "blacklist"
is used improperly in some contexts. Some synonyms fit better.

thanks,
-- 
js
suse labs