# Debian package creates configuration file writable by the elasticsearch process

**URL:** <https://discuss.elastic.co/t/debian-package-creates-configuration-file-writable-by-the-elasticsearch-process/156748>\
**Category:** Elasticsearch\
**Created:** [November 14, 2018, 10:00pm UTC](https://discuss.elastic.co/t/debian-package-creates-configuration-file-writable-by-the-elasticsearch-process/156748 "2018-11-14T22:00:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joost\_Cassee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joost_cassee/32/2156_2.png) [@Joost\_Cassee](https://discuss.elastic.co/u/Joost_Cassee)\
**Post date:** [November 14, 2018, 10:00pm UTC](https://discuss.elastic.co/t/debian-package-creates-configuration-file-writable-by-the-elasticsearch-process/156748/1 "2018-11-14T22:00:18Z")

</div>

I just installed Elasticsearch 6.4.3 on a fresh Ubuntu 18.04 system from the Apt repository. I noticed that the configuration files in `/etc/elasticsearch` are writable by group elasticsearch, which the elasticsearch process runs as.

Is this correct? Configuration is usually only changed by the administrator, not by the application itself. Some applications provide a way to change their own configuration, but I don't this Elasticsearch does.

Any problem restricting access by removing the group writable bits?

Best,  
Joost

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [November 15, 2018, 8:39am UTC](https://discuss.elastic.co/t/debian-package-creates-configuration-file-writable-by-the-elasticsearch-process/156748/2 "2018-11-15T08:39:56Z")

</div>

I _think_ you're right, but please try it out in a safe environment before changing your production environment 🙂 [The intention is that the `elasticsearch` group contains Elasticsearch administrators too.](https://github.com/elastic/elasticsearch/pull/20966#pullrequestreview-4499012) I expect the Java security manager prevents us writing to these files, but I can see a case for using filesystem permissions to clarify that. Would you open an issue at [https://github.com/elastic/elasticsearch/issues](https://github.com/elastic/elasticsearch/issues) to raise this for wider discussion and possible remedy?

---

<div class="post-metadata">

**Author:** ![Joost\_Cassee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joost_cassee/32/2156_2.png) [@Joost\_Cassee](https://discuss.elastic.co/u/Joost_Cassee)\
**Post date:** [November 16, 2018, 12:59pm UTC](https://discuss.elastic.co/t/debian-package-creates-configuration-file-writable-by-the-elasticsearch-process/156748/3 "2018-11-16T12:59:43Z")

</div>

Thanks, I have opened an issue on Github: [https://github.com/elastic/elasticsearch/issues/35634](https://github.com/elastic/elasticsearch/issues/35634)

---

<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:** [December 14, 2018, 12:59pm UTC](https://discuss.elastic.co/t/debian-package-creates-configuration-file-writable-by-the-elasticsearch-process/156748/4 "2018-12-14T12:59:49Z")

</div>

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