nextcloud / nextcloud/end_to_end_encryption
browser: first public link, then share with user - user cannot access
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
- user1 creates e2ee folder, creates public link share ("view and upload") for the folder, someone uploads files via that link
- user1 shares folder with user2 with read write permissions
- user2 accesses the folder - error "Unexpected error: Current user has no access to this folder "
- after this user2 also cannot create new encrypted folders - error
Versions
instance is on NC 33.0.3.2, app end to end encryption 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 listed sequence on Nextcloud 33.0.3.2 with End-to-End Encryption 2.1.1: create a public-link share, upload a file, then share the folder with user2. Trace the access failure and the later encrypted-folder failure. Done means user2 can open the shared folder and create new encrypted folders without either error.
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