Skip to content
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

Umask for documentarians on docs.nyc1.psf.io #186

Open
JulienPalard opened this issue Oct 29, 2019 · 2 comments
Open

Umask for documentarians on docs.nyc1.psf.io #186

JulienPalard opened this issue Oct 29, 2019 · 2 comments

Comments

@JulienPalard
Copy link
Member

@JulienPalard JulienPalard commented Oct 29, 2019

Currently we're all having a umask of 007, so if we create a directory the docsbuild-scripts won't be able to touch it.

@ewdurbin would it be a good idea to set it to 002 (so if we create a directory it would go as 775) and setting S_ISGID (2000) bit on /srv/docs.python.org (and all directory of the herarchy) so anything created under it is still owned by the docs group?

@ewdurbin
Copy link
Member

@ewdurbin ewdurbin commented Oct 29, 2019

That directory isn't currently managed by salt at all, so it can either be set directly by an administrator (such as yourself) or we can configure salt to manage the permissions.

@JulienPalard
Copy link
Member Author

@JulienPalard JulienPalard commented Jan 22, 2020

For the S_ISGID bit we can dot it, yes, but for the umask, do you think it's a good idea to move it from 007 to 002?

I don't know where this strange 007 umask come from on docs.nyc1.psf.io, there's a UMASK 027 in /etc/login.defs, which is not 007, I don't know which part gave me the 0 for the group bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.