owner: gmikcon status: active last_reviewed: 2026-10-03 review_interval: 90d confidence: high
Personal secret storage service with REST API, MCP HTTP/SSE adapter, and Vue UI.
secrets.user_id → users, ON DELETE CASCADE); users cannot see each other's secrets.authenticate_api_token filters revoked_at IS NULL (services.py); last_used_at freezes at the moment of revocation.access.failed audit, key=bearer:<12-char prefix>); cookie auth is only for requests WITHOUT a Bearer header (the SPA). Previously an invalid Bearer fell through to the session cookie in the same request — a revoked token kept "working" inside a logged-in browser (channel=ui), masking revocation. Regression test added (tests/test_auth.py).tokenInvalid flag → popup shows the invalid-token plate on next load. Until then the popup may render the secrets list from chrome.storage.session cache (TTL 5 min, refresh alarm every 15 min) — stale display, not live access.access.failed with key=bearer:<public_id prefix> (the revoked token being rejected), and frozen last_used_at.search_secrets returns ONLY secrets with allow_mcp=true (by design, commit 2082db2: secrets created via MCP always get allow_mcp=true; secrets created via UI/extension default to allow_mcp=false).source = site domain (44 domain-like sources, all alive). The extension creates them via REST (audit channel=rest); there is no channel=extension in audit.metadata snapshot (title, tags, category) forever, including after deletion — deleted secrets remain visible in the audit log under their last known title. Deletion code: gnexus_creds/services.py (audit(..., action="secret.deleted", metadata={"snapshot": ...})).archived=true) and its audit history remains.ip_address in audit for UI traffic via https://creds.gnexus.space shows the internal reverse-proxy IP (192.168.1.226, [[internal-proxy-vps]]), not the real client IP — attribute by user_agent, not by IP.GNEXUS_CREDS_MASTER_KEY_SALT, mandatory in production), field ciphertexts AAD-bound to <user_id>:<secret_id>:<version_id>, hardened destructive endpoints, OAuth state cleanup, MCP arg parsing fixes.python3 -c "import secrets; print(secrets.token_urlsafe(16))", appended GNEXUS_CREDS_MASTER_KEY_SALT=<salt> to .env (master key itself unchanged). Backup of pre-salt .env: .env.pre-salt.GNEXUS_CREDS_CREDS_CORS_ORIGINS=["https://creds.gnexus.space"] — production validator now REJECTS * cors_origins (also validates auth_base_url/auth_redirect_uri/mcp_resource_url must be https).docker compose up -d --build → app healthy.docker compose exec -T app alembic upgrade head → 0001_initial → 0002_notes_widen (secrets.notes 140→255 chars).docker compose exec -T app mkdir -p /app/scripts && docker cp scripts/migrate-crypto.py gnexus-creds-app-1:/app/scripts/ then docker compose exec -T app python scripts/migrate-crypto.py --dry-run (2 keys, 130 ciphertexts) then real run (keys rewrapped 2, field ciphertexts rebound 130), then dry-run again → 0 remaining (idempotent).docker compose logs app first./root/gnexus-creds-backups/backup.sh (root-only, 700) on gnexus-creds-host.pg_dump of the gnexus_creds DB from the running container (gzip) + snapshot of .env — the dump is undecryptable without GNEXUS_CREDS_MASTER_KEY from .env, so both are snapshotted together./root/gnexus-creds-backups/backup.log + cron.log.CREATE TABLE public.secrets, otherwise exit 1.zcat db-*.sql.gz | docker compose exec -T db psql -U gnexus_creds -d gnexus_creds → restore .env → docker compose up -d app. Dumps are --clean/--if-exists, so they can be replayed over an existing schema.extensions/dist/gnexus-creds-extension-{chrome,firefox}-<ver>.zip) and the Dockerfile does COPY extensions ./extensions — so docker compose up -d --build deploys the released extension automatically.docker run --rm -v /home/ubuntu/gnexus-creds:/w -w /w/extensions/extension node:22-bookworm-slim bash -lc "cd ../../frontend && npm ci --no-audit --no-fund && cd ../extensions/extension && make lib && make chrome" (two separate make invocations — make lib chrome in one line fails). Verify with python zipfile CRC comparison against the released zip; git status in extensions/ must stay clean.extensions/pack/, packVersion) is served to installed extensions for hot-update of styling/detection tables without re-releasing..env file in /home/ubuntu/gnexus-creds.GNEXUS_CREDS_ENV=production).SECRET_KEY, MCP_TOKEN) are randomly generated.GNEXUS_CREDS_MASTER_KEY_SALT (mandatory, set 2026-10-03), GNEXUS_CREDS_CORS_ORIGINS=["https://creds.gnexus.space"].docker-compose.yml has an uncommitted local modification that matches the live stack:
postgres $\to$ db (container names gnexus-creds-db-1 / app-1 depend on it);80:8000 (upstream default is 8000:8000);restart: unless-stopped on both services. Preserve it across updates: git stash push docker-compose.yml $\to$ pull $\to$ git stash pop.GET /healthGET /readydocker compose run --rm app alembic upgrade headdocker compose logs -f app.env + docker-compose.yml to ~/backups/ $\to$ stash compose $\to$ git pull --ff-only origin master $\to$ stash pop $\to$ sudo docker compose up -d --build $\to$ alembic upgrade head (only if migrations exist) $\to$ check /health, /ready and https://creds.gnexus.space/health. If app crash-loops with pydantic ValidationError — new production validator requirement, add missing .env var (see Crypto migration section).