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
Setting mode="0000" will prevent vault from modifying the file mode. The expectation is that if a file is already being logged to and read from by something like cwagent or splunk, vault will not rewrite the file mode. However, setting mode="0000" does not yield the intended result, and vault changes the file mode to the default of 0600.
To Reproduce
Steps to reproduce the behavior:
Run touch /opt/vault/vault_audit.log
Run chmod 0644 /opt/vault/vault_audit.log
Run vault audit enable file file_path="/opt/vault/vault_audit.log" mode="0000" or run the terraform config snippet below
Verify file permissions ls -asl /opt/vault/vault_audit.log and see that they have been reverted to the default of 0600
Note that when you set the value to something non-zero, like 0644, it does work as expected. However, setting it to 0000 per the docs does not work as intended.
The text was updated successfully, but these errors were encountered:
Per the vault audit device docs: https://www.vaultproject.io/docs/audit/file#mode
Setting
mode="0000"
will prevent vault from modifying the file mode. The expectation is that if a file is already being logged to and read from by something like cwagent or splunk, vault will not rewrite the file mode. However, settingmode="0000"
does not yield the intended result, and vault changes the file mode to the default of 0600.To Reproduce
Steps to reproduce the behavior:
touch /opt/vault/vault_audit.log
chmod 0644 /opt/vault/vault_audit.log
vault audit enable file file_path="/opt/vault/vault_audit.log" mode="0000"
or run the terraform config snippet belowls -asl /opt/vault/vault_audit.log
and see that they have been reverted to the default of0600
Expected behavior
Vault will not touch the file and leave the permissions as they were:
-rw-r--r--
, or0644
.Environment:
vault status
): 1.8.6+entvault version
): 1.8.6+entVault server configuration file(s):
Note that when you set the value to something non-zero, like
0644
, it does work as expected. However, setting it to 0000 per the docs does not work as intended.The text was updated successfully, but these errors were encountered: