Allow app to specify it doesn't work with user key server side encryption
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
It would make sense if apps can specify they do not work with server side encryption with user keys.
Apps that run not as the user (previewgenerator, richdocuments for example) have now have to somehow hack around this.
- Preview generator just blocks when encryption is enabled
- Richdocuments makes sure files are encrypted with the system key (so as if they are publicly shared)
Both are not ideals and add a lot of weird code.
Apps should not have to care. I don't want to write a lot of encryption checks for apps. I just want to write code with our APIs. So if somebody uses user keys they can't use my app.
@schiessle @nickvergessen @MorrisJobke input please :)
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
Start by tracing how server-side encryption with user keys is detected and enforced in the server APIs, then review the previewgenerator and richdocuments examples described in the issue. Define what app-level declaration and server behavior would be required, and verify that apps no longer need their own encryption checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100