nextcloud / nextcloud/end_to_end_encryption
browser: improve disabling e2ee experience
Open
Nobody has claimed this yet.
0. Needs triage
bug
- 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
- personal settings - security - e2ee
- click reset e2ee
- do not check "delete existing files"
- go to files, click on the e2ee folder - nothing happens, no info. not possible to delete.
Expected behaviour
- folder should be possible to delete
- nice to have: info "you do not have access to this e2ee folder anymore"
- make "delete existing files" checkbox turned on (not off) by default?
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
Reproduce the issue from Personal settings > Security > E2EE by resetting E2EE without deleting existing files, then open the E2EE folder from Files. Trace the reset and folder-delete behavior in the end_to_end_encryption app. Done means the folder can be deleted and the user receives information about losing access; consider the requested default checkbox behavior as part of the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100