Share keys not updated when group members change
@come-nc is already working on this.
Since Feb 11, 2025.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
I run into a critical bug when a folder is shared with a group and group members are updated afterwards.
Steps to reproduce
- disable master key
- enable encryption
- add a new group and at least two additional users
- add yourself and one user to the new group
- share a folder with some stuff with this group
Note:*nextcloud data root*/*user*/files_encryption/keys/files/*folder*/*file*/OC_DEFAULT_MODULE/contains the keys of all group members anddata/admin/files/keys/files/*folder*/*file*is encrypted - add the second user to the group
- remove the first user from the group or delete it
Expected behaviour
After step 7 and 8 the key files should have been updated.
Actual behaviour
The key files are not updated and users that have been added to the group after the folder has been shared are not able to access its content. If a user is removed from the group or deleted, its key file is not cleaned up. This results in a very confusing situation, that after deleting a user and creating a new one with the exact same name, you re not able to share any files again.
This does also happen if you reset the password of a user.
Workaround
The owner of the files has to unsahre all folders and reshare them again after groups memebers have been changed. This is a really bad behavior and not practicable. It's also potential insecure that obsolete keys are not removed.
@nextcloud/encryption is it save to remove any obsolete user.shareKey by hand?
Server configuration
Operating system: any
Web server: any
Database: any
PHP version: 7.3
Nextcloud version: 18
Updated from an older Nextcloud/ownCloud or fresh install: fresh (just for this testcase))
Where did you install Nextcloud from: source
Are you using encryption: yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.