Approval for temporary help
A temporary-ID request cannot relay screen or input until the person at the receiving computer chooses to approve it.
Security model
Trust begins with knowing what the software can—and cannot—do.
No product is unhackable. VeyaDesk separates one-time consent from opt-in permanent access, encrypts session content end to end and documents its boundaries.
Password stays off the relay
Unattended access uses a 15-character minimum and an endpoint-encrypted password proof. The relay never receives the plaintext password or verifier.
Keys stay at the endpoints
P-256 ECDH, signed permanent identities, HKDF-SHA-256 and AES-256-GCM protect and authenticate remote sessions.
DATA PATHENDPOINT ↔ ENDPOINTThe relay handles session routing and encrypted envelopes.
Inside a session
The relay coordinates. The computers encrypt.
Each app creates an ephemeral cryptographic identity for its session. The paired public keys and session ID establish independent send and receive keys. Screen frames and control commands are authenticated before decryption.
Authenticated encryptionAES-256-GCM detects modification and rejects altered content.
Directional keysHost-to-controller and controller-to-host traffic use different keys.
Replay countersRepeated and out-of-order messages are rejected by the receiving app.
Verification wordsBoth people can compare a six-word phrase derived from the session.
Unattended boundary
Permanent access remains explicit and limited.
Unattended access is disabled by default. Enabling it creates a signed permanent device ID and stores private keys plus password-verifier material under current-user Windows DPAPI protection. Five failed passwords trigger independent relay and locally persisted 15-minute lockouts.
Version 0.5 starts only after that Windows user signs in. It is not a system service and cannot control the Windows sign-in screen, UAC secure desktop, BitLocker prompt, a sleeping computer or a powered-off computer.
Deliberate exclusions
Clipboard sync, file transfer, audio, camera access, privilege elevation and secure-desktop control remain unavailable. These capabilities require separate design and review.
Infrastructure boundary
The current relay is a single-instance service that stores active session and online-device state in memory. A restart terminates sessions; enabled hosts automatically re-register.
Current release status
The relay protocol, native encrypted channel, password proof, signed session key and lockout logic have automated checks. Public distribution still requires physical two-computer acceptance testing, code signing and independent security review.
Responsible reporting
Found a security issue?
Please report suspected vulnerabilities privately to [email protected]. Include the affected version, reproduction steps and potential impact. Do not access data that is not yours, disrupt other users, or publicly disclose an unresolved vulnerability.
We will acknowledge valid reports, investigate them and coordinate disclosure when a fix is available. A formal bug-bounty programme is not currently offered.