Security
Link Node runs on people's own computers and accepts
connections from strangers, so we take security reports more seriously
than most projects.
Reporting a vulnerability
Please report vulnerabilities privately through
GitHub's
private vulnerability reporting, for the app as well as the
open-source core. Do not post anything exploitable in public.
We acknowledge reports as fast as we can. This is a small project, but
a vulnerability affects real people's computers, so fixes for anything
serious come before everything else.
Reporting abusive content
A site on a *.mdoc.us address is not hosted by us: it
travels peer-to-peer from the owner's computer. To report phishing, scams
or other abuse, use the report form. Confirmed abuse
can get the address suspended.
What Link Node promises
- One folder, read-only. It serves exactly one
folder and never runs anything in it. Paths cannot leave the folder;
hidden files (
.git, .env, …) and the
instruction files it writes for AI agents are never served. Everything
else in the folder is public.
- Your key stays home. The private key that proves
your address is never sent anywhere. It leaves your computer only when
you copy or export it yourself.
- No remote control. Visitors can open your site,
message you and open what you shared with them. Nothing a visitor or
the Link service sends can change your settings or run anything on your
computer.
- Everything from the network is treated as hostile.
Every read is bounded, every input checked, and every wait has a time
limit.
- The visitor knows it's really you. Your computer
signs every connection with its key, and the visitor's browser checks
that signature before it trusts anything it receives.
Messages and shared folders
- Files attached to messages are checked by their content, not their
name: images, PDF, plain text, Office documents without macros, and ZIP
archives holding no programs or scripts. Anything else is refused and
never stored. Messages are kept in your Inbox folder, which is never
served to anyone.
- A shared folder opens only for the email addresses you list. A
visitor proves their address with a one-time code, and their browser
then holds a key that cannot be copied out of it. Your computer checks
the sign-in and the folder's list on every request, so removing an
address ends that person's access at once.
- A shared folder may never overlap your public folder, your Inbox or
your settings folder.
Known limitation: one shared domain
Each site runs on its own address (<id>.mdoc.us),
which browsers treat as its own origin, but all site addresses share one
registrable domain. A site's scripts can therefore set cookies that
other sites on mdoc.us can read.
- The Link service uses no cookies and keeps no logins on that domain,
and signing in to a shared folder doesn't use cookies either, so this
cannot be used against the service or against your shared folders.
- One site could plant cookies that another one sees. Don't build
anything on your site that relies on cookies for security.
Checking a download
Windows may show a warning the first time the app starts; on a Mac, you allow it once in Settings. You can check a download
against the published checksums; the
open-source core can also be built from
its source.