[PR #4896] [MERGED] Allow custom umask setting #7164

New Issue

GiteaMirror · 2026-03-07T21:12:05-06:00

GiteaMirror commented

2026-03-07 21:12:05 -06:00

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/4896
Author: @BlackDex
Created: 8/26/2024
Status: ✅ Merged
Merged: 8/27/2024
Merged by: @dani-garcia

Base: main ← Head: allow-custom-umask

📝 Commits (1)

6f7d7a6 Allow custom umask setting

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 docker/start.sh (+4 -0)

📄 Description

To provide a way to add more security regarding file/folder permissions this PR adds a way to allow setting a custom UMASK variable.

This allows people to set a more secure default like only allowing the owner the the process/container to read/write files and folders.

Examples:

UMASK=022 File: 644 | Folder: 755 (Default of the containers)
This means Owner read/write and group/world read-only
UMASK=027 File: 640 | Folder: 750
This means Owner read/write, group read-only, world no access
UMASK=077 File: 600 | Folder: 700
This means Owner read/write and group/world no access

resolves #4571

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/dani-garcia/vaultwarden/pull/4896 **Author:** [@BlackDex](https://github.com/BlackDex) **Created:** 8/26/2024 **Status:** ✅ Merged **Merged:** 8/27/2024 **Merged by:** [@dani-garcia](https://github.com/dani-garcia) **Base:** `main` ← **Head:** `allow-custom-umask` --- ### 📝 Commits (1) - [`6f7d7a6`](https://github.com/dani-garcia/vaultwarden/commit/6f7d7a6ff94a53fb5ceb2922552adbe94c178e6f) Allow custom umask setting ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docker/start.sh` (+4 -0) </details> ### 📄 Description To provide a way to add more security regarding file/folder permissions this PR adds a way to allow setting a custom `UMASK` variable. This allows people to set a more secure default like only allowing the owner the the process/container to read/write files and folders. Examples: - `UMASK=022` File: 644 | Folder: 755 (Default of the containers) This means Owner read/write and group/world read-only - `UMASK=027` File: 640 | Folder: 750 This means Owner read/write, group read-only, world no access - `UMASK=077` File: 600 | Folder: 700 This means Owner read/write and group/world no access resolves #4571 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-03-07 21:12:05 -06:00

GiteaMirror closed this issue

2026-03-07 21:12:07 -06:00

GiteaMirror referenced this issue

2026-04-30 08:25:23 -05:00

[PR #7164] [MERGED] Fix merge conflict #22091

GiteaMirror referenced this issue

2026-05-22 02:25:32 -05:00

[PR #7164] [MERGED] Fix merge conflict #24772

Sign in to join this conversation.