[
https://issues.apache.org/jira/browse/CASSANDRA-15862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15862:
----------------------------------------
Change Category: Code Clarity
Complexity: Low Hanging Fruit
Component/s: Legacy/Core
Fix Version/s: 4.0-alpha
3.11.x
3.0.x
2.2.x
Assignee: Sam Tunnicliffe
Status: Open (was: Triage Needed)
> 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
> Components: Legacy/Core
> Reporter: Ash Berlin-Taylor
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0-alpha
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
