nextcloud / nextcloud/end_to_end_encryption
End-to-End Encryption in the browser, editor shows encrypted content
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 320
- Forks
- 36
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 81
Description
I enabled end-to-end encryption in the browser and uploaded a file:
I would expect that all editors/viewers are disabled and clicking on a file starts a download. Instead the normal texteditor opens and shows the encrypted filename and the encrypted content:
Also creating new documents should be disabled because this fails as well, probably because it wants to open the corresponding editor during document creation:
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
Reproduce the browser workflow with end-to-end encryption enabled, then trace the file-opening and new-document flows that still invoke the normal editor. Done means encrypted files are downloaded instead of displayed and creating a document does not fail by opening an unavailable editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100