-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Don't use the term "whitelist" - language matters #9174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
It's fairly common to say whitelisting and blacklisting to describe desirable and undesirable things in cyber security. However just because it is common doesn't mean it's right. However, there's an issue with the terminology. It only makes sense if you equate white with 'good, permitted, safe' and black with 'bad, dangerous, forbidden'. There are some obvious problems with this. You may not see why this matters. If you're not adversely affected by racial stereotyping yourself, then please count yourself lucky. For some of your friends and colleagues (and potential future colleagues), this really is a change worth making. From now on, we will use 'allow list' and 'deny list' in place of 'whitelist' and 'blacklist' wherever possible. Which, in fact, is clearer and less ambiguous. So as well as being more inclusive of all, this is a net benefit to our understandability. (Words mostly borrowed from <https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white>)
|
There are a few references left over.
It is probably worth adding a check for this: |
|
Added PR to automate the check #9175. I managed to remote the pylintrc entry there (and removed optional whitelist from a comment in webserver_config example of Google Oauth) |
|
Thanks @potiuk -- I've pulled that commit in to here, and added a |
|
Yep. Closing this one. |
|
Wrong one :) |
|
Yep |
|
Just quarantined tests failing. |
|
Thanks Ash :) This is great to see! |
|
I was just going to make this PR - so glad you beat me to it!! |
|
For anyone who is doubting this change or curious as to the history of the words, the U.S. Library of Medicine has detailed etymology |
It's fairly common to say whitelisting and blacklisting to describe
desirable and undesirable things in cyber security. Just because
it is common doesn't mean it's right.
However, there's an issue with the terminology. It only makes sense if
you equate white with 'good, permitted, safe' and black with 'bad,
dangerous, forbidden'. There are some obvious problems with this.
You may not see why this matters. If you're not adversely affected by
racial stereotyping yourself, then please count yourself lucky. For some
of your friends and colleagues (and potential future colleagues), this
really is a change worth making.
From now on, we will use 'allow list' and 'deny list' in place of
'whitelist' and 'blacklist' wherever possible. Which, in fact, is
clearer and less ambiguous. So as well as being more inclusive of all,
this is a net benefit to our understandability.
(Words mostly borrowed from
https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white)
Closes #9175
Make sure to mark the boxes below before creating PR: [x]
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.