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
The infrastructure.salt.master state sets file permissions for /etc/salt/gpgkeys/** to 0600, which should be good practice.
Unfortunately some other tool (GPG or Salt?) sets the S.gpg-agent* socket permissions back to 0700 - leading to a "back and forth" whenever the formula state is applied, and prevents a state.test run from returning fully green.
I do not want to implement an exception for this in the formula as I'm not aware of any reason for Unix sockets to be executable.
It should be examined which software is setting the permissions to 0700 and if there's a way to prevent it.
On my Tumbleweed workstation the stock GnuPG creates the S.gpg-agent socket with mode 0600.
The text was updated successfully, but these errors were encountered:
The infrastructure.salt.master state sets file permissions for /etc/salt/gpgkeys/** to 0600, which should be good practice.
Unfortunately some other tool (GPG or Salt?) sets the S.gpg-agent* socket permissions back to 0700 - leading to a "back and forth" whenever the formula state is applied, and prevents a state.test run from returning fully green.
I do not want to implement an exception for this in the formula as I'm not aware of any reason for Unix sockets to be executable.
It should be examined which software is setting the permissions to 0700 and if there's a way to prevent it.
On my Tumbleweed workstation the stock GnuPG creates the S.gpg-agent socket with mode 0600.
The text was updated successfully, but these errors were encountered: