Encrypt Filenames SSE
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Currently, if you enable server-side encryption (SSE) and I suspect by extend end-to-end encryption (E2EE) names of files are not encrypted. I think this is a major oversight and should be fixed because filenames can give a lot of information about the content stored in a file. File names (and even folder names) can contain private and/or personal information, like names of persons, places bank accounts present, etc. Even highly sensitive data like gender or sexual orientation can be exposed via unencrypted filenames
This fact is also stated in the official manual, so this is obviously "intended behaviour" but severely limits the application of SSE impov.
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 with the linked official server-side encryption documentation and compare its stated filename behavior with the issue’s SSE and E2EE expectations. Identify the encryption paths that govern file and folder names; done means the intended metadata-protection behavior is defined and verified for both filenames and folder names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100