docs: add file permissions guidance to hardening page#14922
Open
skjnldsv wants to merge 1 commit into
Open
Conversation
Contributor
📖 Documentation Preview📄 1 changed documentation pageLast updated: Wed, 20 May 2026 07:23:44 GMT |
skjnldsv
force-pushed
the
fix/harden-server-file-permissions
branch
from
48828f5 to
18770ce
Compare
Adds a new 'Set strong file permissions' subsection to the Deployment section of harden_server.rst. The permissions section was removed in PR #431 because the web updater needs write access to the install dir, but no replacement guidance was added. This restores the guidance with the tradeoff clearly documented: - baseline chmod/chown commands for read-only install dir - note that data/ and apps/ must stay writable - note that web updater must be disabled (upgrade.disable-web) before applying stricter install-dir permissions Fixes #1353 Signed-off-by: skjnldsv <skjnldsv@protonmail.com> Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
skjnldsv
force-pushed
the
fix/harden-server-file-permissions
branch
from
18770ce to
d9b3ad9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
Summary
The hardening page had no file permission guidance. The permissions section was removed in PR #431 because the web updater requires write access to the Nextcloud directory, but no replacement guidance was added and the tradeoff was never documented.
This adds a new "Set strong file permissions" subsection to the Deployment section covering:
chown/chmodcommands to make the install directory read-only for the web server userdata/must remain writable by the web server userapps/must remain writable if using the app store'upgrade.disable-web' => truemust be set before applying stricter permissionsNote: regarding the paths used, there is a discussion to unify those here: #11447
🖼️ Screenshots
✅ Checklist
codespellor similar and addressed any spelling issues