nextcloud / nextcloud/end_to_end_encryption
browser: moving/copying a file from e2ee folder to non-e2ee folder results in encrypted file
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 320
- Forks
- 36
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 81
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Steps to reproduce
- have an e2ee folder with one file inside
- copy or move the file to another folder
- the file ends up there with encrypted filename and content
Expected behaviour
option 1:
- show warning "the file will be stored in the new location unencrypted - proceed?"
- store the file in the new location unencrypted
option 2:
show info that file cannot be moved to unencr folder, only to e2ee folders)
sidenote
copying/moving the file to the root folder results in a normal, decrypted file. Probably intended?
versions
Nextcloud: 33.0.5
e2ee app: 2.1.1
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 reproducing the copy and move steps with an E2EE folder and a non-E2EE folder on the reported Nextcloud 33.0.5 and E2EE app 2.1.1 versions. Trace the server app's file operation handling and compare it with moving to the root folder. Done means the behavior is explicitly handled: the file is safely decrypted with a warning, or the operation is prevented with a clear message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100