Go to file
Michael Mainguy 2aac38146d vrek: ISAPI snapshot findings, retire met goals
- Record that camera …af54 has no full-resolution still over ONVIF or
  ISAPI (fnd-dw1pqcw, fnd-k1jyt83); close iss-3vck3js.
- Retire gol-2nxgqjn, and gol-wqf95dq and gol-8v1wqvp as met on one
  user observation each.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-19 15:08:50 -05:00
.idea Track vrek export, MCP config and IDE VCS mapping 2026-09-19 08:52:49 -05:00
.vrek vrek: ISAPI snapshot findings, retire met goals 2026-09-19 15:08:50 -05:00
public Initial commit from Create Next App 2026-09-19 07:15:19 -05:00
scripts Add admin login foundations: scrypt admin file, CLI, sessions 2026-09-19 09:46:40 -05:00
src Add camera pop-out window 2026-09-19 15:02:39 -05:00
test Reach 99.8% test coverage and enforce a 95% floor 2026-09-19 09:17:55 -05:00
.gitignore Add camera pop-out window 2026-09-19 15:02:39 -05:00
.mcp.json Track vrek export, MCP config and IDE VCS mapping 2026-09-19 08:52:49 -05:00
AGENTS.md Initial commit from Create Next App 2026-09-19 07:15:19 -05:00
CLAUDE.md Initial commit from Create Next App 2026-09-19 07:15:19 -05:00
eslint.config.mjs Initial commit from Create Next App 2026-09-19 07:15:19 -05:00
next.config.ts Add image and stream editing with audit log, manual exposure controls 2026-09-19 14:44:00 -05:00
package-lock.json Add image and stream editing with audit log, manual exposure controls 2026-09-19 14:44:00 -05:00
package.json Add image and stream editing with audit log, manual exposure controls 2026-09-19 14:44:00 -05:00
postcss.config.mjs Initial commit from Create Next App 2026-09-19 07:15:19 -05:00
README.md Enforce admin login: login, first-run setup, proxy and access checks 2026-09-19 11:58:20 -05:00
tsconfig.json Add admin login foundations: scrypt admin file, CLI, sessions 2026-09-19 09:46:40 -05:00
vitest.config.mts Add Lucide icons: camera status badge, actions and warnings 2026-09-19 12:33:16 -05:00

Cameras

A web interface for discovering and managing Hikvision and Annke IP cameras on your local network.

Securing the web interface

The dashboard and its API are protected by a single admin login. The login is stored in a file, never in plain text: the password is hashed with scrypt (random salt, N=65536, r=8, p=1), so it can't be recovered from the file.

Setting Default
ADMIN_AUTH_FILE (environment variable, e.g. in .env.local) ./.data/admin.json

If the file doesn't exist, the app starts unsecured: anyone who can reach it can view your cameras and change their logins. To avoid ever running it that way, create the admin file before the first start (below).

Setting it up from the browser instead

With no admin file, the server prints a one-time setup code in its console at startup:

====================================================================
  No admin login is set up: the camera dashboard is NOT secured.

  To secure it from a browser, open /setup and enter this one-time code:

      XLZ7-Q4MB
  ...

Opening the app sends you to /setup, which asks for that code plus the new admin username and password. Only someone who can see the server console can claim the login. After 5 wrong codes a new one is printed.

You can also choose Skip for now and run unsecured. Every page then shows a red warning banner, the API stays open to anyone on the network, and the setup prompt returns the next time the browser is restarted.

Signing in

Once an admin exists, every page and API call needs a session: pages redirect to /login, and the API answers 401. A session lasts 12 hours from your last activity. After 10 wrong passwords from one address (or 100 from all addresses) within 15 minutes, logins are paused for up to 15 minutes. Sign out (top right) ends the session in that browser; to sign out everywhere, change the password.

npm run admin:create

It asks for a username and a password (at least 12 characters; typing is hidden, and you confirm it), then writes the file with owner-only permissions (0600). Options:

npm run admin:create -- --username admin      # only ask for the password
npm run admin:create -- --force               # replace the existing admin (reset the password)
printf '%s\n' "$PW" | npm run admin:create -- --username admin   # non-interactive, e.g. provisioning

Without npm: a Node one-liner

Any Node 24+ can produce the same file. The password is read from the terminal without echoing, so it never appears in your shell history or the process list:

(read -rs PW && export PW && umask 077 && mkdir -p .data && node -e '
const c = require("node:crypto"), N = 65536, r = 8, p = 1, salt = c.randomBytes(16);
const key = c.scryptSync(process.env.PW, salt, 64, { N, r, p, maxmem: 256 * N * r });
const passwordHash = ["scrypt", N, r, p, salt.toString("base64"), key.toString("base64")].join("$");
console.log(JSON.stringify({ version: 1, username: "admin", passwordHash }, null, 2));
' > .data/admin.json)

The parentheses run it in a subshell, so the password variable and the stricter umask end with it.

Change username: "admin" to taste. Usernames are 1–64 letters, digits, or . _ @ -.

File format

{
  "version": 1,
  "username": "admin",
  "passwordHash": "scrypt$65536$8$1$<salt, base64>$<64-byte key, base64>"
}

A file that exists but is malformed stops the app from authenticating anyone rather than quietly turning security off; fix it or delete it.

Forgot the password?

Run npm run admin:create -- --force (or delete the file and create it again). Changing the password signs out every existing session.


This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.