nextcloud / nextcloud/documentation
Document user key draw backs (SSE)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
One suggestion from my side. We should mention that user keys have some draw backs which can easily irritate users.
A example I use all the time: Think about a group share, the moment you share a file with a group Nextcloud will take the public keys of all group members and encrypt the file-key with it. With large groups this can have a (huge) performance impact. If a admin adds later additional users to the group they will see the file shared with the group but they will not be able to decrypt it because they where not part of the group when the file-key was encrypted. This can lead to a lot of confusion and 1st level support request like "i can't open a file shared with me", "nextcloud is broken", etc.
Originally posted by @schiessle in https://github.com/nextcloud/documentation/issues/13754#issuecomment-3429268380
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.
Research direction
No documentation file or entry point is named. Start by locating the user-key or SSE documentation, then explain the group-share performance impact and why users added to a group later may not decrypt existing shared files. Done means these drawbacks are clearly documented for users and support staff.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100