GHGatehousePublic alpha
Documentation/Security

Security

Deny by default at every trust boundary

A signed-in web session does not itself authorize a private request. The relay requires a short-lived capability and rechecks session, grant, service, connector, method, expiry, and revocation state.

01

What the alpha mitigates

Public port exposure, broad network access, reused enrollment tokens, arbitrary proxy targets, metadata IP SSRF, stale connector epochs, and unauthenticated console access.

02

Secret handling

Account passwords use salted scrypt hashes. Browser sessions and relay capabilities use separate HMAC keys. Connector credentials are hashed in PostgreSQL and stored locally by the agent.

03

Remaining limitations

The alpha does not claim compliance certification, phishing resistance, device trust, regional failover, or compatibility with every application origin policy.