You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ash Berlin-Taylor (Jira)" <ji...@apache.org> on 2020/06/07 20:42:00 UTC

[jira] [Created] (CASSANDRA-15862) Use "allow list" or "safe list" instead of the term "whitelist"

Ash Berlin-Taylor created CASSANDRA-15862:
---------------------------------------------

             Summary: Use "allow list" or "safe list" instead of the term "whitelist" 
                 Key: CASSANDRA-15862
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15862
             Project: Cassandra
          Issue Type: New Feature
            Reporter: Ash Berlin-Taylor


Language matters. I'd like to remove all references in Apache Airflow to whitelist or black list, and the Cassandra Python API has some that we can't easily remove.

The recent global events have made this even more relevant, but this has been on my radar for a while now. Here is a well written article for why I think it matters 

https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white

{quote}It's fairly common to say whitelisting and blacklisting to describe desirable and undesirable things in cyber security.

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. {quote}

My exposure to is via the Python API where there is the cassandra.pollicies.WhiteListRoundRobinPolicy class. I propose that this be renamed to AllowListRoundRobinPolicy instead. I do not know if there are other references.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org