{"version":"2.1.284","anchor":"vouched-gateway-hosts-no-longer-get-a-network-fingerprint-pi","canonical_anchor":"vouched-gateway-hosts-no-longer-get-a-network-fingerprint-pi","heading":"Gateway hosts vouched for by a recognized deployment skip network pinning","tier":"internal","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/vouched-gateway-hosts-no-longer-get-a-network-fingerprint-pi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Gateway hosts vouched for by a recognized deployment skip network pinning\n\nA gateway host can now be accepted because a recognized deployment vouches for it, and those hosts are not pinned to a network fingerprint\n\n**Unclear.** It is not clear what uses this gateway check or how a deployment comes to vouch for a host.\n\n**What**\n\nA gateway is a server that Claude Code's network requests pass through. When Claude Code checks whether a gateway host can be trusted, it can now accept the host because a recognized deployment vouches for it. When a host is accepted this way, Claude Code does not pin it to a network fingerprint. A network fingerprint is a record of which network the host was verified on. Hosts verified in the usual way are still pinned as before.\n\n**Why**\n\nThis appears to be part of a new way to trust a gateway host. In practice, vouched hosts are not tied to the network they were first checked on.\n\n- Area: Gateway\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}