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

Set a more restrictive default umask #23

Merged
merged 1 commit into from
Mar 19, 2024
Merged

Conversation

Dunedan
Copy link
Collaborator

@Dunedan Dunedan commented Mar 18, 2024

By default Debian uses a umask of 022, which results in newly created files being world readable. That's not desired for our use case, as we want to restrict access of different users, especially the lobby bots, as much as possible. Therefore, this changes the default umask from 022 to 077 to ensure only the creator of a file can access it by default.

When updating an existing lobby server, the file permissions for already existing lobby bots have to be updated manually to make use of the more restrictive permissions.

By default Debian uses a umask of 022, which results in newly created
files being world readable. That's not desired for our use case, as we
want to restrict access of different users, especially the lobby bots,
as much as possible. Therefore, this changes the default umask from 022
to 077 to ensure only the creator of a file can access it by default.

When updating an existing lobby server, the file permissions for already
existing lobby bots have to be updated manually to make use of the more
restrictive permissions.
@Dunedan Dunedan merged commit 8ba20e3 into 0ad:master Mar 19, 2024
1 check passed
@Dunedan Dunedan deleted the umask-077 branch March 19, 2024 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant