Sabo
August 30, 2024, 6:23am
1
I am using Nextcloud AIO with the latest updates on my Debian 12 server.
Nextcloud version 3.13.2git
Git revision f0ab45748f296ff00856d54be97a1d58988cd540
Using Qt 5.15.14, built against Qt 5.15.14
Using Qt platform plugin 'wayland'
Using 'OpenSSL 3.2.2 4 Jun 2024'
Running on Fedora Linux 40 (Workstation Edition), x86_64
The Nextcloud sync always changes the permissions of directories to 777 after some time - even if I explicitly set it to 755.
This is not wanted and could In some cases even be a security risk.
How can I fix this issue?
I see the same issue on my linux client; whenever Nextcloud client synchronizes a file, the parent directories have their permissions changed to rwxrwxrwx.
I don’t understand why the permissions are changed.
My versions:
nextcloud-client: 3.13.3-1 (manjaro)
nextcloud: 29.0.6
1 Like
The following issue looks similar:
opened 05:27PM - 30 Jun 24 UTC
closed 02:03PM - 09 Sep 24 UTC
2. to review
bug
regression
feature:
stable-3.13
### ⚠️ Before submitting, please verify the following: ⚠️
- [X] This is a **b… ug**, not a question or a configuration issue.
- [X] This issue is **not** already reported on Github (I've searched it).
- [X] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)
### Bug description
After updating from 3.13.0 to 3.13.1, this error occurs.
If a file is updated in an existing folder, the permissions are modified for all folders directly above it up to the sync root folder, the folders become writable for groups and others.
Another way is to simply create a new folder for example in the sync root folder. Directly after creation, the folder then has the following rights, for example `drwx------ 2 user user 4096 Jun 30 19:14 test`. After the folder was synchronized, the rights have now changed, in this example `drwx-w--w- 2 user user 4096 Jun 30 19:14 test`.
There are no log entries for either the server or the client.
After downgrading from 3.13.1 to 3.13.0, this error no longer occurs.
### Steps to reproduce
1. Create a new folder with only read, write and execute permission for the user.
2. After the synchronization is complete check the permissions
3. The permissions changed to allow the group and other to write to the folder
---
1. Create a new file in a previously created folder (older client versions) and check that this folder only has read, write and execute permission for the user.
2. Create a new file in this folder or modify an existing one.
4. After the synchronization is complete check the permissions of the folder
5. The permissions changed to allow the group and other to write to the folder
### Expected behavior
After the synchronization no folder permissions are changed.
### Which files are affected by this bug
custom created test folder
### Operating system
Linux & macOS
### Which version of the operating system you are running.
Arch Linux & Debian 12
### Package
Distro package manager & AppImage
### Nextcloud Server version
29.0.3
### Nextcloud Desktop Client version
3.13.1 & 3.13.2 & 3.12.3
### Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
### Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
### Are you using an external user-backend?
- [x] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Nextcloud Server logs
_No response_
### Additional info
_No response_
It seems it is fixed but not released yet…
1 Like