# User could see other people's password

**URL:** <https://forum.search-guard.com/t/user-could-see-other-peoples-password/52>\
**Category:** Search Guard\
**Created:** [June 23, 2015, 9:54am UTC](https://forum.search-guard.com/t/user-could-see-other-peoples-password/52 "2015-06-23T09:54:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lingxiao\_Xia](https://avatars.discourse-cdn.com/v4/letter/l/9de053/32.png) [@Lingxiao\_Xia](https://forum.search-guard.com/u/Lingxiao_Xia)\
**Post date:** [June 23, 2015, 9:54am UTC](https://forum.search-guard.com/t/user-could-see-other-peoples-password/52/1 "2015-06-23T09:54:24Z")

</div>

It seems to me user could access search guard configuration, suppose the elasticsearch instance is at 127.0.0.1:9200

“curl -XGET [http://user:name@127.0.0.1:9200/\_nodes?pretty](http://user:name@127.0.0.1:9200/_nodes?pretty)” returns all information about search guard, including a list of username/password configured in searchguard.authentication.settingsdb.user.\*

it’s odd because then user1 could know user2’s password or any other user’s password, is this the intended behavior?

---

<div class="post-metadata">

**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\
**Post date:** [June 23, 2015, 6:34pm UTC](https://forum.search-guard.com/t/user-could-see-other-peoples-password/52/2 "2015-06-23T18:34:40Z")

</div>

you can use searchguard.authentication.settingsdb.digest to avoid plain text passwords for now.

Next version will separate this usernames and passwords from the elasticsearch.yml file cause its also odd that you have to restart cluster nodes if the password change 🙂

> **···**
>
> Am Dienstag, 23. Juni 2015 11:54:24 UTC+2 schrieb Lingxiao Xia:
> 
> > It seems to me user could access search guard configuration, suppose the elasticsearch instance is at [127.0.0.1:9200](http://127.0.0.1:9200)
> 
> > “curl -XGET [http://user:name@127.0.0.1:9200/\_nodes?pretty](http://user:name@127.0.0.1:9200/_nodes?pretty)” returns all information about search guard, including a list of username/password configured in searchguard.authentication.settingsdb.user.\*
> 
> > 
> 
> > it’s odd because then user1 could know user2’s password or any other user’s password, is this the intended behavior?

---

<div class="post-metadata">

**Author:** ![grizzlys85](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@grizzlys85](https://forum.search-guard.com/u/grizzlys85)\
**Post date:** [September 9, 2015, 3:07pm UTC](https://forum.search-guard.com/t/user-could-see-other-peoples-password/52/3 "2015-09-09T15:07:59Z")

</div>

Hello!  
But what about LDAP connection?

Unfortunately LDAP bind password also shown to every user.

> **···**
>
> вторник, 23 июня 2015 г., 21:34:40 UTC+3 пользователь [in...@search-guard.com](mailto:in...@search-guard.com) написал:
> 
> > Next version will separate this usernames and passwords from the elasticsearch.yml file cause its also odd that you have to restart cluster nodes if the password change 🙂
> > 
> > Am Dienstag, 23. Juni 2015 11:54:24 UTC+2 schrieb Lingxiao Xia:
> > 
> > > It seems to me user could access search guard configuration, suppose the elasticsearch instance is at [127.0.0.1:9200](http://127.0.0.1:9200)
> 
> > > “curl -XGET [http://user:name@127.0.0.1:9200/\_nodes?pretty](http://user:name@127.0.0.1:9200/_nodes?pretty)” returns all information about search guard, including a list of username/password configured in searchguard.authentication.settingsdb.user.\*
> 
> > >
> 
> > > it’s odd because then user1 could know user2’s password or any other user’s password, is this the intended behavior?
> 
> > you can use searchguard.authentication.settingsdb.digest to avoid plain text passwords for now.

---

<div class="post-metadata">

**Author:** ![grizzlys85](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@grizzlys85](https://forum.search-guard.com/u/grizzlys85)\
**Post date:** [September 9, 2015, 3:09pm UTC](https://forum.search-guard.com/t/user-could-see-other-peoples-password/52/4 "2015-09-09T15:09:22Z")

</div>

and “truststore\_password” also shown

> **···**
>
> среда, 9 сентября 2015 г., 18:07:59 UTC+3 пользователь [grizz...@gmail.com](mailto:grizz...@gmail.com) написал:
> 
> > Hello!  
> > But what about LDAP connection?
> 
> > Unfortunately LDAP bind password also shown to every user.
> > 
> > вторник, 23 июня 2015 г., 21:34:40 UTC+3 пользователь [in...@search-guard.com](mailto:in...@search-guard.com) написал:
> > 
> > > Next version will separate this usernames and passwords from the elasticsearch.yml file cause its also odd that you have to restart cluster nodes if the password change 🙂
> > > 
> > > Am Dienstag, 23. Juni 2015 11:54:24 UTC+2 schrieb Lingxiao Xia:
> > > 
> > > > It seems to me user could access search guard configuration, suppose the elasticsearch instance is at [127.0.0.1:9200](http://127.0.0.1:9200)
> 
> > > > “curl -XGET [http://user:name@127.0.0.1:9200/\_nodes?pretty](http://user:name@127.0.0.1:9200/_nodes?pretty)” returns all information about search guard, including a list of username/password configured in searchguard.authentication.settingsdb.user.\*
> 
> > > >
> 
> > > > it’s odd because then user1 could know user2’s password or any other user’s password, is this the intended behavior?
> 
> > > you can use searchguard.authentication.settingsdb.digest to avoid plain text passwords for now.
