You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to improve security (and, to a minimal extent, performance), it would be great to be able to configure Vault Proxy to use unix sockets:
listener"unix" {
address="/var/run/vault.sock"
}
and then specify:
unixSocket: /var/run/vault.sock
Rather than:
serverHost: localhostserverPort: 8200
As it stands, any user able to access that port (e.g. via kubectl port-forward) can easily make authenticated requests to Vault via port 8200. Being able to send requests via a unix socket would improve the situation.
The text was updated successfully, but these errors were encountered:
I'm currently running a Vault Proxy sidecar alongside Web3Signer to handle auth and forward requests to Vault.
Each key file looks something like this:
In order to improve security (and, to a minimal extent, performance), it would be great to be able to configure Vault Proxy to use unix sockets:
and then specify:
Rather than:
As it stands, any user able to access that port (e.g. via
kubectl port-forward
) can easily make authenticated requests to Vault via port 8200. Being able to send requests via a unix socket would improve the situation.The text was updated successfully, but these errors were encountered: