Open-source desktop project Pre-release

The person at the screen stays in charge.

Name: JDoor
Author: Djenis Ejupi

JDoor began as a 2022 school networking project. Its rebuild replaced invisible remote access with a visible host, short-lived pairing, local approval and a session that starts view-only by default.

See one session Read the source

Remote helper asks to view Link shared privately

Host device

Mode View only

Local
decision

The project

It began by connecting two computers. The rebuild changed the question.

JDoor was co-created by Djenis Ejupi and NobodyToListen as a school experiment in networking and remote control. The first version proved the connection could work. Years later, Djenis rebuilt it around a narrower and more useful premise: the person sharing the machine should remain visibly present in every decision.

Then / prove the connection: An unauthenticated remote-access prototype focused on moving screen and input data between two machines.
Now / define the boundary: A short-lived invitation, an exact endpoint check, local approval and permission that belongs only to the current session.

The modernization covers product direction, security, UX, testing and release engineering while preserving the project’s shared origin.

A session

One session, from invitation to screen sharing.

The application checks the route and constrains the protocol. Both people compare the same code; the host makes the final decision.

Host / prepare

Create a short-lived invitation

The host creates a fresh P-256 certificate, its exact SHA-256 fingerprint and a random 128-bit token that expires after 10 minutes.

People / share

Send the complete link privately

The host sends the one-time jdoor:// link to the intended helper through a separate, trusted channel.

Client / check

Check the destination

The helper’s application checks the advertised host and exact certificate fingerprint before presenting the single-use token inside TLS 1.2/1.3.

People / decide

Compare the code and approve

Both computers show the same verification code. The host reviews the request and approves it on the machine being shared.

Session / view

Show the screen without control

Primary-display frames begin only after approval. Remote input stays disabled unless the host enables it for that session.

Trust & privacy

The software checks the endpoint. The host decides the person.

Connection evidence can narrow a request to one machine. Trust in the person—and every permission that follows—remains a local decision.

Software checks

Connection evidence

Endpoint: Exact SHA-256 certificate pin for the advertised host
Invitation: Random 128-bit token, single-use and short-lived
Protocol: TLS 1.2/1.3 plus explicit type, size and range bounds

The host decides

Human permission

Person: Whether the helper behind the checked endpoint is expected
Capability: Whether to remain view-only or enable mouse and keyboard input
End: When to revoke control or stop the session immediately

Local audit / not a recording

JDoor has no telemetry, analytics, crash upload, account service or public relay. It keeps a bounded local trail of security events—not a copy of the screen or what was typed.

Local trail: Time, event type, remote address and a short lifecycle description.
Never content: No tokens, private keys, screen pixels, typed content or raw input events.
Retention: Daily JSONL, capped at 5 MiB and retained by the app for 30 days.

Limits

The missing features are deliberate.

JDoor is for one person helping another on a trusted local network. It is not an internet-facing remote-management platform, and it does not hide an administration layer behind the support session.

Designed for

A visible, approved session

Direct connection on a trusted LAN
One approved viewer
Primary-display sharing
Optional, revocable input
Local, bounded audit events

Not part of JDoor

Administration in the background

Unattended access or persistence
Remote shell or privilege escalation
File or clipboard transfer
Webcam, microphone or stealth capture
Public relay, accounts or NAT traversal

Network boundary. Use JDoor only on a trusted LAN, share the complete pairing link through a separate trusted channel and do not expose port 8443 directly to the internet.

Residual risk. An approved helper can see the shared display and, while the host enables control, act through the host’s existing user session.

Current status

Pre-release

JDoor is currently a pre-release codebase.

The source, architecture, threat model and privacy documentation are available for inspection. Community builds are unsigned and may trigger an unverified-publisher warning. If you are evaluating the project, begin with the threat model and build the desktop application locally.

Inspect the repository Build it locally