# Security

The dashboard is a remote control for your computer, and it is built that way:

- It listens on this computer only until you choose otherwise. On a network it speaks plain HTTP, so use a network
  you trust; on the internet use the public link (HTTPS through the tunnel) or `hoprig setup --hub`, which puts it
  behind HTTPS and refuses plain HTTP.
- One password stored as a scrypt hash, one-time sign-in links, HttpOnly SameSite=Strict cookies, an Origin check
  on every change, a strict content security policy. The public link asks for a strong password before it turns on.
- Five wrong passwords and a visitor waits: this computer counts as one visitor whatever local address it uses,
  every visitor through the public link counts on its own, a limit for all wrong passwords together never locks
  this computer out, and a one-time sign-in link has its own count, so guesses do not lock it.
- When the dashboard reads a project's git state (Source Control, quick open, the chat's `@` files, the project
  counts), the repository's own settings never start a program: hooks, filters, diff and signature programs are
  switched off for that read. A git command a coding tool runs is the coding tool's own.
- Installs, updates, downloads and the demo get an environment without provider keys; the tunnel helper is checked
  against its known SHA-256 before it is used.
- Another computer gets a token you can revoke. A token cannot change the password, pair, or relay further.
- The router listens on 127.0.0.1 under a secret path and keeps no request or answer text.
- The editor and the desktop's Files reach only the folders the dashboard may show (**Settings → Security and
  sign-in** sets them, or everything your user can open); every path is checked on the server. Private folders
  (`no-ai`, `ignore`, `ai-ignore-dir`), git's own folder, the dashboard's own folders and sign-in files are never
  shown, searched or changed.
- A file of a project shown as a page runs in a sandbox. A shared gateway's keys are kept as hashes, and only `/v1/`
  paths pass.
- The administrator password for a setup step or a service is asked in the page when `sudo` needs it, given to
  `sudo` on its input, and never saved or shown.
- OpenCode's server, which Hoprig starts for a chat, listens on this computer only and always with a password; its
  routes that would return a key never reach the browser. A provider's key is given to a coding tool in its
  environment when it starts, never written into the tool's own files.
- Provider files (sign-ins and keys), tokens and passwords are readable by your user only and are never printed,
  logged or sent to a browser. Found a problem? See [SECURITY.md](https://github.com/allswebtech/hoprig/blob/main/SECURITY.md).

---

This page on the web: https://hoprig.com/docs/security/ · Every page: https://hoprig.com/llms.txt
