Runtime log retention
Login, preview, and file actions produce logs in the desktop app or headless output, which systemd journal can collect. Retention depends on deployment settings; there is no separate persistent or tamper-evident audit store.
Manual
Access protection and deployment boundaries
Login, preview, and file actions produce logs in the desktop app or headless output, which systemd journal can collect. Retention depends on deployment settings; there is no separate persistent or tamper-evident audit store.
Security: Access protection and deployment boundaries
Before deployment, confirm the shared folder, allowed network sources, account permissions, and backup plan.Shared-folder boundary
The server resolves requested paths and rejects access outside the shared root. Sensitive files placed inside that root are still shared; choose a dedicated folder.
Filename checks
Upload, create, rename, and download requests extract the base name, replace special characters, and reject an empty result. Windows also rejects reserved device names. Sanitization can change the name; check the resulting file.
Upload size and disk space
The default limit is 512 MiB per upload request, including all selected files and multipart overhead. Set a positive integer in maxUploadMb to change it. This limit is not a disk quota; check available disk space before uploading.
Large-file transfer
Downloads stream at speeds limited by the network, disk, and client. Interrupted downloads must restart; resume is unsupported.
Accounts and sessions
Passwords use salted hashes; cookies use HttpOnly and SameSite=Lax. Sessions expire 12 hours after login by default. Desktop password changes do not revoke sessions; stop and restart sharing to clear them. HTTP has no transport encryption; deploy on a controlled LAN or VPN.
Deployment checklist
Use a dedicated shared folder, keep access on the LAN, fix the port, remove unused accounts, restrict delete permission, clean temporary files, and follow the latest downloads page for package access.