hashicorp / hashicorp/consul

Consul cluster auto join - vsphere Password exposed [Vsphere/Vmware]

Open
#7,343 6 comments 0 reactions 1 assignee Claimed by @jsosulska View on GitHub
type/question
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
2d 6h
Merged PRs (30d)
43

Description

We have a Consul cluster in VMware.

**Issue:-** when I do ps -ef | grep consul, I am able to see the actual password. How to overcome this issue.

**Consul Version :- 1.2.2**

**PS Output:-**
root 11136 1 0 Feb24 ? 00:00:00 /bin/sh -c /opt/consul/bin/consul agent -config-dir /opt/consul/config/ -retry-join "provider=vsphere category_name=consul-server tag_name=consul-server-sandbox host=example.com user=temp-consul-svc-acct@vsphere.local password=**Password Exposed here** insecure_ssl=true" 2>&1 >> /opt/consul/logs/consul.log

Below is our service file.
> [Unit]
> Description=Consul
> Documentation=https://consul.io/docs
> Wants=network-online.target
> After=network-online.target
> StartLimitIntervalSec=10
>
> [Service]
> EnvironmentFile=/etc/environment
> KillMode=process
> KillSignal=SIGINT
> ExecStart=/bin/sh -c '/opt/consul/bin/consul agent -config-dir /opt/consul/config/ -retry-join "provider=${CLOUD_PROVIDER} category_name=${VSPHERE_TAG_CATEGORY} tag_name=${VSPHERE_TAG} host=${VSPHERE_HOST} user=${VSPHERE_USER} password=${VSPHERE_PASS} insecure_ssl=true" 2>&1 >> /opt/consul/logs/consul.log'
>
> ExecReload=/bin/kill -HUP $MAINPID
> Restart=on-failure
> RestartSec=2
> StartLimitBurst=3
> LimitNOFILE=65536
>
> [Install]
> WantedBy=multi-user.target

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.