Mac Desktop client - folder permissions

uselpa · July 10, 2024, 9:18pm

Hi

i have impression that in the last days, possibly since using mac desktop client 3.13.2, folder permissions have gone from 755 to 777. I’ve checked this with
find . -type d -perm 0777 -ls.
My umask os still 0022 though. It also only seems to affect folders, since
find . -type f -perm 0777 -ls
shows nothing. Also, on the Nextcloud server itself the folders all have the same 755 permissions.

Has anybody else observed this? You need to look in a terminal session, the Finder won’t show this.
Is this a parameter somewhere (other than umask)? I haven’t found anything appropriate in the documentation.

I will have to do more extensive tests but if anybody could confirm or point me to the right documentation it would be helpful.

Regards,
-Patrick

mritzmann · July 11, 2024, 10:42am

github.com/nextcloud/desktop

[Bug]: Folder permissions are changed during synchronization

opened 05:27PM - 30 Jun 24 UTC

TopMax

0. Needs triage

### ⚠️ Before submitting, please verify the following: ⚠️ - [X] This is a **bug…**, 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 ### Which version of the operating system you are running. Arch Linux ### Package Distro package manager ### Nextcloud Server version 29.0.3 ### Nextcloud Desktop Client version 3.13.1 ### 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_

uselpa · July 11, 2024, 11:16am

Thanks @mritzmann , I should have looked there in the first place.

uselpa · August 5, 2024, 2:15pm

Since the bug is currently not being addressed, what is the best way to downgrade the macOS client from 3.13.2 to 3.13.0?
I have downloaded Nextcloud-3.13.0.pkg but simply installing that package does not work, so before doing it “my way ;-)” I was wondering if there is a generally recommended way?