Keamanan
FlashDesk nglindhungi sambungan remot nganggo enkripsi end-to-end, verifikasi piranti, lan persetujuan sing cetha.
Komunikasi dienkripsi
Data layar, input, lan kontrol dilindhungi enkripsi sesi nganggo pertukaran kunci ECDH lan AES-GCM. Saben sambungan nganggo kunci sing beda.
P2P utawa relay otomatis
Yen bisa, piranti nyambung langsung. Yen perlu relay, payload media lan kontrol tetep dienkripsi ing lapisan sesi.
Akses remot mbutuhake persetujuan
Kasedhiya persetujuan manual, sepisan, winates wektu, utawa mode sandhi. Piranti panampa mung nampa sambungan sing wis diidini.
Identitas lan fingerprint piranti
FlashDesk nggunakake identitas lan fingerprint piranti supaya sampeyan bisa ngenali piranti sing padha ing sambungan sabanjure.
Signaling mung kanggo nggawe sambungan
Server signaling digunakake kanggo nemokake piranti, negosiasi, lan status. Server ora perlu maca payload layar utawa input sing dienkripsi.
Sertifikat TLS eksternal
Komunikasi signaling FlashDesk nggunakake WebSocket liwat HTTPS / TLS. Informasi sertifikat TLS publik ing ngisor iki dijupuk saka server lan dianyari otomatis nalika sertifikat diganti.
- Domain
- Ngunggah informasi sertifikat...
- Penerbit
- Ngunggah informasi sertifikat...
- Fingerprint SHA-256
- Ngunggah informasi sertifikat...
- Kadaluarsa
- Ngunggah informasi sertifikat...
Informasi sertifikat sauntara ora kasedhiya.
Pangujian keamanan eksternal
FlashDesk wis ngrampungake pangujian keamanan kanggo situs web umum lan endpoint sing gegandhengan nganggo OWASP ZAP. Kita uga wis mesthekake rating A utawa luwih dhuwur ing Mozilla Observatory, SSL Labs, lan Security Headers.
Proteksi informasi sing disimpen
Informasi sambungan lan sandhi sing disimpen diproses supaya ora disimpen minangka teks polos.
Data sing ditangani server FlashDesk
FlashDesk servers may handle the following information as needed for service operation, abuse prevention, support, billing, and team administration.
| Data | Purpose | Stored or temporary | Notes |
|---|---|---|---|
| FlashDesk ID / device identifier | Connection start, device lookup, license association | Stored where needed | Used to identify devices and route requests. |
| Device fingerprint public information | Device verification and ID binding | Stored as a hash where applicable | The server stores fingerprint-related hashes, not the private identity key. |
| App version and OS type | Compatibility, support, and operational analysis | Stored or updated with client status | Shown in admin and support contexts where applicable. |
| Connection status and path status | Connection maintenance, seat control, admin visibility | Temporary during sessions; selected audit records for Pro | Includes whether a session is direct, relay, or probing when reported. |
| IP address and network metadata | Service operation, abuse prevention, diagnostics | Stored in operational records where needed | May include last seen IP, download tracking, and WebSocket diagnostic metadata. |
| License / subscription status | License verification, billing, seat management | Stored where needed | Payment card details are handled by the payment provider, not by FlashDesk. |
| Error logs or operational logs | Support, outage investigation, abuse prevention | Stored as operational logs; server logs are automatically deleted after 30 days | WebSocket logs redact ssh_tunnel_data payloads; other metadata may be logged for diagnostics. |
| Admin console activity for Pro users | Team administration, license and session review | Stored as admin records | Includes organization, user, license, seat, and session audit records. |
Data sing ora disimpen server FlashDesk
FlashDesk servers do not store the following information during ordinary remote connections:
- remote screen video contents
- keyboard input contents
- mouse operation contents
- file transfer contents
- SSH tunnel payload contents handled as ssh_tunnel_data
- recorded session video contents
Endpoint jaringan lan protokol
The following table summarizes communication that administrators may want to review before deployment.
| Purpose | Protocol | Port | Typical destination | Notes |
|---|---|---|---|---|
| Website / download | HTTPS | 443/TCP | FlashDesk official servers | Download pages show the version and SHA-256 checksum for official release files. |
| Signaling | WebSocket over TLS (wss://) | 443/TCP | flashdesk.io/ws | Used to start sessions and exchange candidate information. |
| API / license check | HTTPS | 443/TCP | flashdesk.io/api/license/verify | Used when checking a registered license key and seat status. |
| Update check | HTTPS | 443/TCP | flashdesk.io/data/latest.json and package paths | The app periodically checks the update manifest over HTTPS, downloads update packages from official servers, and verifies the expected SHA-256 hash before applying an update. |
| STUN / P2P candidate check | UDP | 3478/UDP | FlashDesk official servers | Used to discover a reachable network endpoint before attempting direct P2P. |
| Direct P2P connection | UDP media/control path | Dynamic UDP ports on peer devices | Peer device network endpoints | Direct connection is preferred when NAT/firewall conditions allow it. |
| Relay connection | Encrypted media/control payloads over the relay path | 40020/UDP in the current desktop app | FlashDesk relay server | Used when a direct device-to-device path is not available. SDK relayws responses use 443/TCP. |
Prilaku server relay
FlashDesk first attempts a direct device-to-device path. Because NAT, firewall, VPN, and mobile-network conditions can prevent direct UDP communication, sessions may continue through a relay path when needed.
When relay routing is used, the relay server forwards packets for the session. Media and control payloads continue to be encrypted with the per-session key, and packets include authentication data used to detect tampering or replayed old packets.
Instalasi lan prilaku latar mburi
FlashDesk can run in the background and can start automatically with the OS when the setting is enabled. The current default setting enables OS startup.
- Windows: startup is managed through a user logon scheduled task named FlashDesk_Autostart, with a legacy Run-key fallback check.
- macOS: startup is managed through a LaunchAgent plist.
- Linux: startup is managed through XDG Autostart.
OS permissions are requested only as needed for features. macOS may require Screen Recording for screen capture and Accessibility for remote input control. Linux Wayland sessions use the desktop portal / PipeWire screen-sharing flow. FlashDesk periodically checks an HTTPS update manifest, downloads update packages from official servers, and verifies the expected SHA-256 hash before applying an update.
Local settings are stored under the user's application data folder in FlashDesk/flashdesk_settings.json. Local app logs are written under the user's local application data folder in FlashDesk/logs with a 7-day retention setting in the current app code. Local screen recordings, when enabled by the user, are stored under FlashDesk/recording on the user's device.
Keaslian file lan code signing
Download pages show the version and SHA-256 checksum for official release files. Before installation, users can compare the downloaded file's SHA-256 checksum with the value published on the download page.
- Windows: FlashDesk .exe files are signed with Authenticode. You can check the signature from file Properties > Digital Signatures, or run
Get-AuthenticodeSignature .\FlashDesk.exein PowerShell. - macOS: FlashDesk .pkg and .app distributions are signed with Apple Developer ID certificates and notarized by Apple.
- Linux: verify the published SHA-256 checksum for .deb, .rpm, and AppImage downloads.
Laporan kerentanan
Kanggo masalah keamanan, gunakake kaca kontak kanthi [Security] ing subject.
Please include the affected version, OS, reproduction steps, logs if available, and screenshots if relevant.
Panggunaan sing disaranake
Wenehana akses mung marang wong sing dipercaya, priksa jeneng lan fingerprint piranti, lan gunakake persetujuan cekak kanggo bantuan sementara.