Skip to content

fix: verify TLS for deployment RPCs - #65

Draft
Alicepoltora wants to merge 1 commit into
SeismicSystems:mainfrom
Alicepoltora:agent/deploy-tls-verification
Draft

fix: verify TLS for deployment RPCs#65
Alicepoltora wants to merge 1 commit into
SeismicSystems:mainfrom
Alicepoltora:agent/deploy-tls-verification

Conversation

@Alicepoltora

Copy link
Copy Markdown

Summary

  • keep certificate and hostname verification enabled for HTTPS RPC calls
  • stop silently probing and downgrading bare hostnames from HTTPS to HTTP
  • route staking and checkpoint RPC calls through the hardened client
  • add regression tests for HTTPS verification and URL normalization

Why

The deployment RPC helpers disabled TLS verification for every URL, including production HTTPS hostnames. This allowed an on-path attacker to spoof bootstrap, checkpoint, or staking responses. The URL normalizer also silently fell back from HTTPS to HTTP when a bare host probe failed.

Bare IP inputs retain the existing explicit HTTP behavior; secure deployments should use an https:// URL.

Validation

  • uv run ruff check deploy_gcp/seismic_deploy/network/bootnode.py deploy_gcp/seismic_deploy/network/stake.py deploy_gcp/seismic_deploy/network/sync.py deploy_gcp/seismic_deploy/network/test_bootnode.py
  • uv run ty check deploy_gcp/seismic_deploy/network/bootnode.py deploy_gcp/seismic_deploy/network/stake.py deploy_gcp/seismic_deploy/network/sync.py deploy_gcp/seismic_deploy/network/test_bootnode.py
  • uv run python -m unittest discover -s deploy_gcp -p 'test_*.py' -v
  • python3 -m compileall -q deploy_gcp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant