You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release fetches use HTTPS only, with loopback HTTP for fixtures #314
Part of #311 (Group C, security hardening). Owner: not assigned. Task base and PR target: develop. Start after #313 merges (same installer file).
Intended behavior
The installer and the Runtime fetch release data from public hosts over HTTPS only. Plain HTTP is accepted only for loopback addresses, which test fixtures use.
Current behavior
Signatures protect integrity, but the transport has no protocol limit.
install.sh calls curl -fsSL without --proto or --proto-redir for the release head (line 1100), the release (line 1134), IPFS gateway fetches (line 627) and the binary download (step 3, near line 1180). A redirect can move a fetch to http://.
The Runtime's HTTP download client (download_http_client, elastos/crates/elastos-server/src/update.rs:367-372) accepts any scheme for --gateway, --no-p2p and gateway fallbacks.
release-signer.py:379 already requires an https:// publisher gateway in the stamped installer, so this change matches existing policy.
The CI hop serves fixtures over http://127.0.0.1 (scripts/update-hop-compare.py).
The Runtime refuses non-loopback http:// gateway URLs with a clear error. Test: a unit test in update.rs for http://example.org (refused) and http://127.0.0.1:port (accepted). Note: at aa3d61e updates no longer download over HTTP (no --gateway or --no-p2p option); Anders decides whether this item is still needed.
Done, closed with proof: items 1 and 3 are proven above. Item 2 no longer applies (Anders, 15 Oct): since alpha.15 the Runtime has no HTTP gateway download path (--gateway, --no-p2p and the HTTP download client were removed; updates come only over Carrier). Leftover for 0.8.1 under #173: live_source_bootstrap_ticket (carrier.rs:1005) does not require https; the ticket must still match the publisher node ID.
Activity
andersalm commentedon Oct 15, 2026
Done, closed with proof: items 1 and 3 are proven above. Item 2 no longer applies (Anders, 15 Oct): since alpha.15 the Runtime has no HTTP gateway download path (
--gateway,--no-p2pand the HTTP download client were removed; updates come only over Carrier). Leftover for 0.8.1 under #173:live_source_bootstrap_ticket(carrier.rs:1005) does not require https; the ticket must still match the publisher node ID.