-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows support: review permissions in directories and files created #3189
Comments
Since #3227 introduces more restrictive permissions in agent and server data directories (granting access to the owner only), I would like to collect some feedback to know if this could cause any problem. |
Thanks for contacting me @amartinezfayo - I've inspected the change and nothing in there stands out to me as an issue, however, it would be great if there is a build available so I can quickly deploy it on a few of our Windows machines. If you could please point me to a build and also detail the spire-server version requirement for the build, I can verify the change for you next week. Thanks! |
Thank you @nweedon-u, that would be great! |
Thanks! I will test against a v1.3.x installation later this week. |
Hey @amartinezfayo, I've tested your build on Windows Server 2012 and Windows Server 2019 and I can't see any problems - the agents seem to connect fine to our spire-server instances and the directories get populated with the expected data. Thanks! |
Thank you very much for taking the time to test this, @nweedon-u! |
Identified work items are:
|
This issue is stale because it has been open for 365 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
SPIRE creates some directories that store sensitive data, with certain permissions to restrict access (e.g. agent and server data directories).
On Windows, those directories are created with the CreateDirectory function using a NULL security descriptor. As a result, the directory gets a default security descriptor and the ACLs are inherited from its parent directory.
This means that the end user must take into account the ACLs of the directory where SPIRE is deployed, to properly secure sensitive data stored by SPIRE.
I think that a better security posture (considering that we strive to keep a "secure by default" policy) would be to set a security descriptor that would restrict access to the creator owner only in those directories.
The text was updated successfully, but these errors were encountered: