Files
web-terminal/relay-auth/test/audit.test.ts
Yaojia Wang 2af57e6686 feat(relay): rendezvous-relay service — 7 packages + plans (contracts/transport/agent/control-plane/e2e/auth/web)
Multi-tenant reverse-tunnel service ("ngrok for Claude Code" with E2E): a
host-agent dials OUT to an operator-run relay; external devices reach the host
THROUGH the relay, routed by per-tenant subdomain, forwarding ciphertext only
(the relay never sees plaintext). Lets a customer reach their own self-hosted
web-terminal from anywhere with zero networking setup.

Packages — all tsc-strict + vitest green (656 tests), cross-package integration verified:
- relay-contracts: frozen shared contracts (mux frame codec, data model,
  capability token, E2E envelope, pairing) — the src/types.ts analog
- term-relay:   native WS mux + stateless data plane (subdomain routing, ciphertext forward)
- agent:        host-agent (pairing, per-host Ed25519 + mTLS dial-out, forwards to 127.0.0.1:3000)
- control-plane: accounts/hosts registry, pairing-code flow, routing table, provisioning
- relay-e2e:    browser<->agent E2E (X25519 ECDH through relay, AEAD, anti-replay, recoverable replay key)
- relay-auth:   Passkey/WebAuthn, capability tokens, per-host certs, deny-by-default tenant isolation
- relay-web:    browser login + Web Crypto E2E + client-side preview rendering

Security invariants INV1-15 enforced; cross-tenant isolation CI tripwire live
(.github/workflows/relay-tripwire.yml). Design + implementation-level plans in
docs/PLAN_RELAY_*.md and docs/EXPLORE_RELAY_SERVICE.md.

NOTE: generated autonomously per the reviewed plans. The security-critical
packages (relay-e2e, relay-auth) REQUIRE expert security audit before any real
deployment — passing tests prove self-consistency, not resistance to attackers.
Base app (src/, public/) unchanged; concurrent desktop work left uncommitted.
2026-07-02 06:10:16 +02:00

95 lines
2.7 KiB
TypeScript
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

import { describe, it, expect } from 'vitest'
import { buildAuditEvent, audit } from '../src/audit/log.js'
import { assertZeroPayload, ZeroPayloadViolation } from '../src/audit/redact.js'
import type { AuditEvent, AuditSink } from '../src/types.js'
import { principal, fakeAuditSink } from './_helpers.js'
const NOW = 1_700_000_000
describe('audit log (INV10)', () => {
it('builds a well-formed attach allow event and appends it', async () => {
const sink = fakeAuditSink()
const e = buildAuditEvent({
action: 'attach',
principal: principal('acct-A'),
hostId: 'host-1',
sessionId: null,
jti: 'jti-1',
outcome: 'allow',
reason: 'ok',
remoteAddrHash: 'hash',
now: NOW,
})
await audit(sink, e)
expect(sink.events).toHaveLength(1)
expect(sink.events[0]!.action).toBe('attach')
expect(sink.events[0]!.accountId).toBe('acct-A')
})
it('records a deny event with a reason', () => {
const e = buildAuditEvent({
action: 'cross-tenant-attempt',
principal: null,
hostId: 'host-B',
sessionId: null,
jti: null,
outcome: 'deny',
reason: 'cross_tenant',
remoteAddrHash: 'hash',
now: NOW,
})
expect(e.outcome).toBe('deny')
expect(e.reason).toBe('cross_tenant')
expect(e.principalId).toBe('')
})
it('throws (zero-payload guard) when a field contains ESC bytes', () => {
const e: AuditEvent = {
ts: new Date(NOW * 1000).toISOString(),
action: 'attach',
principalId: 'p',
accountId: 'a',
hostId: null,
sessionId: null,
jti: null,
outcome: 'allow',
reason: 'output:' + String.fromCharCode(0x1b) + '[31mred',
remoteAddrHash: 'h',
}
expect(() => assertZeroPayload(e)).toThrow(ZeroPayloadViolation)
})
it('throws when a field exceeds the metadata length cap', () => {
const e: AuditEvent = {
ts: new Date(NOW * 1000).toISOString(),
action: 'attach',
principalId: 'p',
accountId: 'a',
hostId: null,
sessionId: null,
jti: null,
outcome: 'allow',
reason: 'x'.repeat(300),
remoteAddrHash: 'h',
}
expect(() => assertZeroPayload(e)).toThrow(ZeroPayloadViolation)
})
it('audit() refuses to append a payload-bearing event', async () => {
const bad: AuditEvent = {
ts: new Date(NOW * 1000).toISOString(),
action: 'attach',
principalId: 'p',
accountId: 'a',
hostId: ']0;title',
sessionId: null,
jti: null,
outcome: 'allow',
reason: 'ok',
remoteAddrHash: 'h',
}
const sink: AuditSink = { append: async () => undefined }
await expect(audit(sink, bad)).rejects.toThrow(ZeroPayloadViolation)
})
})