1. TheOneFile
  2. Security
Security

Lose your head, not your data

Your network documentation is a map for attackers. TheOneFile keeps it on your machine, in one file, encrypted if you want it. No server, no account, no cloud.

An encrypted One File asking for its password before anything is shown
The same file after unlocking, showing the full homelab map

Encryption inside the file

Turn on encryption and every save is locked before it is written. Without the password the file shows nothing but a lock screen.

AES 256 GCM

Authenticated encryption through the browser’s own Web Crypto API. Nothing to install, nothing sent anywhere.

600,000 key iterations

Your password is stretched with PBKDF2 and 600,000 iterations. Older files remember their own settings, so they still open.

No recovery, by design

There is no backdoor and no reset. Lose the password and the data stays locked. Keep it somewhere safe.

Nothing left in plain sight

Encrypted saves get a generic title and filename, keep no selected node details, and leave no plain text copy in rollback history, autosave or the port map.

Explains itself

Opened from a plain http address where the browser blocks Web Crypto, the file tells you why instead of throwing an error.

Safe to share

A map someone sends you should never be able to run code. Versions 4.2.0 and 4.2.0 closed every path we found.

  • Notes are cleaned before they show, and Core and Networkening share one note cleaner
  • Port Map and Recordings can no longer run code hidden inside a shared file
  • Imported files cannot sneak in a custom language that runs scripts, or tamper with built in objects
  • A node name containing a closing script tag can no longer break out of the saved file
  • Images and backgrounds from other websites wait until you choose Load remote image
  • Recordings and tab names from imported files are checked before they are used
  • Icons are checked and cleaned before they reach the canvas

Private by default

  • Core makes no network requests at all, so it is safe on air gapped machines
  • Networkening only reaches out to fetch icons you browse and to run the status checks you turn on. Opening a file with auto ping asks before it starts
  • Custom ping URLs are limited to http and https
  • This website sets no cookies and loads nothing from third parties

TheOneFile_Verse, locked down

When you self host TheOneFile_Verse, the server is hardened too.

Server side roles

Every change is checked against the sender’s role on the server, for WebSockets and HTTP alike. View only means view only.

Secrets encrypted

AES 256 GCM for stored secrets, including two factor secrets and backup codes, with the key kept in a protected key file.

Request protection

Probes, webhooks and the SMTP test refuse loopback, metadata and private targets where they do not belong. Webhooks no longer follow redirects.

Sign in hardening

Two factor codes on magic link and SSO sign in, constant time code checks, verified email for account linking and https only OIDC endpoints.

Room data checked

Ids, colours and recordings are checked on the way in and out, with a parse5 backed sanitizer that falls back to plain text.

Limits for guests

Guest rooms capped at 5 MB each and 300 in total, an instance room limit and storage quotas, all adjustable.

Read the full list in the changelog and the TheOneFile_Verse changelog.