nextcloud / nextcloud/end_to_end_encryption
Renaming a file in a e2ee share folder not possible
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
- open a e2ee share folder with files in it
- choose rename a file via the 3-dot menu
- file shows cryptic name instead of real file name
- rename the file results in error
This behavior is the same for the person who can upload a file and also the person who shares the e2ee folder.
Expected behaviour
- When choosing rename the filename should be shown not the cryptic name.
- Renaming should be possible for both sides. Sharer and Uploader
Actual behaviour
Error: Could not rename "filename"
Server configuration
Operating system: Linux
Web server: Apache
Database: Postgres
PHP version:
Nextcloud version: NC 33.0.7 (see Nextcloud admin page)
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from: Nextcloud AIO
If not, provide at least the version number of the End-to-End-Encryption app.
E2EE App Version 2.2.2
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 rename flow in an E2EE share folder with End-to-End-Encryption app 2.2.2, testing both the person who uploads and the person who shares the folder. Trace the server-side rename handling from the three-dot menu; done means the real filename is shown and renaming succeeds for both sides.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100