Skip to content

chore(keys): remove the retired AWS gateway from the index #170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sanity merged 1 commit into from
Sep 4, 2026
Merged

chore(keys): remove the retired AWS gateway from the index #170

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 0 additions & 29 deletions hugo-site/static/keys/gateways.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,32 +28,3 @@ public_key = "keys/public.gw2.pem"

[gateways.address]
hostname = "gw2.freenet.org:31338"

# Secondary gateway on independent infrastructure (AWS, different provider,
# different /24, different uplink). Still running; retirement is pending.
#
# Addressed by bare IP deliberately. The name it used to carry was under a
# personal domain, and this box is being shut down, so a new DNS record for it
# would be churn for nothing. `hostname` with an IP literal resolves without
# touching a DNS resolver at all (std's ToSocketAddrs parses it directly).
#
# `hostname` rather than `host_address` because it is the shape already in this
# file and is covered by a back-compat test pinned against the deployed copy,
# and because an IP literal resolves without touching a resolver at all.
#
# NOT for fail-soft reasons. An earlier revision of this comment claimed a bad
# `hostname` would degrade to one gateway failing at dial time. That is FALSE:
# `parse_socket_addr(..).await?` runs INSIDE the per-gateway loop
# (freenet-core node.rs:587), so a single unresolvable entry aborts
# NodeConfig::new and the node does not start. Any entry here can take every
# peer down on restart. Treat all three as equally load-bearing.
#
# REMOVE THIS ENTRY when the box is actually shut down. Until then it is the
# only listed gateway outside the host that runs gw1 and gw2, so dropping it
# early would leave every refetching peer with a bootstrap set confined to a
# single machine, IP, uplink and datacenter.
[[gateways]]
public_key = "keys/public.vega.gw.pem"

[gateways.address]
hostname = "100.27.151.80:31337"
Loading