Desktop-Anwendung zum gleichzeitigen Hochladen auf mehrere File-Hoster
Two isolated hardenings of the opt-in remote/diagnostics WS server, surfaced by the session-wide diagnostics audit: 1. WebSocketServer was created with no maxPayload, so ws defaults to 100 MiB per message. The connection handler runs JSON.parse(raw) on the FIRST message (the auth frame) before authentication, so any peer past the IP allowlist could send a huge payload and force a synchronous multi-MB JSON.parse on the main-process event loop — an unbounded freeze/DoS sink. Diag, auth and WebRTC signaling messages are all small; cap maxPayload at 256 KiB to close it. 2. sendToClient did ws.send(JSON.stringify(data)) with no readyState/try guard (unlike broadcast, which checks ws.readyState === 1). A send on a closing socket, or a stringify throw, escaped the diag-response callback as an uncaughtException — a potential crash. Mirror broadcast: send only when readyState === 1, wrapped in try/catch. Both are isolated to the transport layer with zero redaction surface. The audit's larger finding — server_health doing O(historySize) synchronous work per request (6-7 full-config clones + unbounded history walks) — is a real freeze, but ONLY on the cold opt-in diagnostics path with a large history (this user: 23 rows), and the safe fix cuts into the credential-redaction collectors (which have leaked twice); deferred and documented in tasks/todo.md rather than operated under risk. 397/397 tests pass, eslint clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| assets | ||
| docs | ||
| gateway | ||
| lib | ||
| renderer | ||
| scripts | ||
| tasks | ||
| tests | ||
| .gitignore | ||
| app.py | ||
| eslint.config.mjs | ||
| hosters.py | ||
| main.js | ||
| package-lock.json | ||
| package.json | ||
| preload-drop-target.js | ||
| preload.js | ||
| README.md | ||
| requirements.txt | ||
Multi-Hoster-Upload
Desktop-Anwendung zum gleichzeitigen Hochladen von Dateien auf mehrere File-Hosting-Dienste.
Unterstuetzte Hoster
- doodstream.com - API-Key basiert
- voe.sx - API-Key basiert
- vidmoly.me - Login basiert (Username/Passwort)
- byse.sx - API-Key basiert
Installation
Setup (empfohlen)
Lade die Multi-Hoster-Upload Setup X.X.X.exe aus den Releases herunter und installiere.
Portable
Lade die Multi-Hoster-Upload X.X.X.exe herunter. Keine Installation noetig.
Entwicklung
npm install
npm start
Build
npm run release:win
Erzeugt Setup + Portable EXE im release/ Ordner.
Release
GITEA_TOKEN=dein_token npm run release:gitea -- 1.0.1 "Release notes"
Features
- Drag & Drop oder Dateiauswahl
- Gleichzeitiger Upload zu mehreren Hostern
- Echtzeit-Fortschrittsanzeige
- Ergebnis-Tabelle mit Sortierung und Kopier-Funktion
- Upload-Verlauf (letzte 100 Eintraege)
- Health-Check fuer Hoster-Verbindungen
- Auto-Updater (prueft git.24-music.de)
- Log-Datei kompatibel mit File & Image Uploader Format