os_https_fetch.sg is the HTTPS pipeline capstone — it wires TLS 1.3 (os_tls.sg) into the network handler IPC ring so the browser can load real https:// URLs. The end-to-end pipeline: DNS resolve → TCP connect → TLS 1.3 handshake → encrypted HTTP GET → response decryption → IPC response to browser tab. All tests PASS on QEMU raspi3b.
HTTPS fetch bridge
os_https_fetch.sg
HTTPS detection + TLS bridge — detects
https:// scheme (port 443), routes through TLS handshake before HTTP fetch. Bridges the NH (network handler) IPC ring with the TLS layer — incoming NET_REQUEST for HTTPS URLs triggers: (1) DNS resolve via os_net_resolve, (2) TCP connect to resolved IP:443, (3) TLS 1.3 ClientHello/ServerHello via os_tls, (4) encrypted HTTP GET, (5) response decryption, (6) NET_RESPONSE back to browser tab. Dispatcher structure ready for ChaCha20-Poly1305 live decryption.Complete network stack
The browser→OS network path now has every layer from URL to encrypted response:
browser tab → IPC NET_REQUEST → os_net_handler → os_net_resolve (DNS) → os_https_fetch (scheme detect) → os_tls (TLS 1.3 handshake) → encrypted GET → decrypt → NET_RESPONSE → browser tab
Remaining: real ChaCha20-Poly1305 AEAD crypto (currently stubbed), x25519 key exchange, certificate chain verification against trust anchors.