Reusing filenames can cause files to become unintentionally shared
- Vorherrschende Sprache
- Python
- Sterne
- 46.6k
- Forks
- 1.9k
- Ø Merge
- 10 T. 16 Std.
- Gemergte PRs (30 T.)
- 5
Beschreibung
### Describe the bug
If you share a file, that share key can be used to access to any future file with the same filename.
### To Reproduce
1. Upload a file with a particular filename
2. Create a share for the file
3. Delete the file
4. Upload a different file (i.e. different contents) with the same filename
5. Dereference the share link
### Expected behavior
The share link 404s, and listing the share key results in 0 files.
### Server details (if you're NOT using docker/podman)
* **server OS / version:** Debian bookworm
* **what copyparty did you grab:** sfx
* **how you're running it:** init
* run copyparty with `--version` and grab the last 3 lines (they start with `copyparty`, `CPython`, `sqlite`) and paste them below this line:
copyparty v1.19.15 "usernames" (2025-09-29)
CPython v3.11.2 on Linux64 6.1.140 [GCC 12.2.0]
sqlite 3.40.1*1 | jinja 2.11.3 | pyftpd 1.5.10 | tftp 0.4.0
* **copyparty arguments and/or config-file:** `-e2ds -e2ts --shr /shared` (not complete)
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.