# Language matters - blacklist\_ and whitelist\_

**URL:** <https://discuss.elastic.co/t/language-matters-blacklist-and-whitelist/298803>\
**Category:** Logstash\
**Created:** [March 4, 2022, 2:14am UTC](https://discuss.elastic.co/t/language-matters-blacklist-and-whitelist/298803 "2022-03-04T02:14:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![eclctcjp](https://avatars.discourse-cdn.com/v4/letter/e/e19b73/32.png) [@eclctcjp](https://discuss.elastic.co/u/eclctcjp)\
**Post date:** [March 4, 2022, 2:14am UTC](https://discuss.elastic.co/t/language-matters-blacklist-and-whitelist/298803/1 "2022-03-04T02:14:38Z")

</div>

For the prune filter, please change to more neutral language the 4 values:  
blacklist\_names  
blacklist\_values  
whitelist\_names  
whitelist\_values

I noticed this post, but it looks like we missed the settings in "prune"

> [@Removal of non-inclusive terms "whitelist" with neutral language](https://discuss.elastic.co/t/removal-of-non-inclusive-terms-whitelist-with-neutral-language/276780):
>
> Hi, Kibana has a configuration property elasticsearch.requestHeadersWhitelist. There are concerns raised on usage of this non-inclusive terminology. Linux team has approved on replacing these non-inclusive terminologies. There are many other tech companies and open-source projects that have removed references to racially-charged jargon from their code for more neutral and inclusive language. Reference: [Linux team approves new terminology, bans terms like 'blacklist' and 'slave' | ZDNet](https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/) This …

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [March 4, 2022, 2:39am UTC](https://discuss.elastic.co/t/language-matters-blacklist-and-whitelist/298803/2 "2022-03-04T02:39:43Z")

</div>

There is already a github [issue](https://github.com/logstash-plugins/logstash-filter-prune/issues/28) for this. Sounds like they were hoping to get this (and the Elasticsearch output change) into 8.0, but they did not do so. The meta issue is [here](https://github.com/elastic/logstash/issues/12052).

It might have to wait for 9.x to get a breaking change like this to be implemented. (Obviously I do not speak for Elastic.)

---

<div class="post-metadata">

**Author:** ![eclctcjp](https://avatars.discourse-cdn.com/v4/letter/e/e19b73/32.png) [@eclctcjp](https://discuss.elastic.co/u/eclctcjp)\
**Post date:** [March 4, 2022, 1:06pm UTC](https://discuss.elastic.co/t/language-matters-blacklist-and-whitelist/298803/3 "2022-03-04T13:06:10Z")

</div>

Thanks for the info @Badger

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 1, 2022, 1:06pm UTC](https://discuss.elastic.co/t/language-matters-blacklist-and-whitelist/298803/4 "2022-04-01T13:06:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.