How It Works
gdirect solves the challenge of accessing Google Drive in regions where Google domains are blocked, such as mainland China. Instead of routing full transfer bandwidth through VPNs or proxy tunnels, it probes Google's published IP ranges (goog.json minus cloud.json) for accessible front-end servers. When direct TLS handshakes fail due to SNI filtering, gdirect falls back to forged TLS identities (presenting g.cn during TLS negotiation while preserving the true destination in the HTTP Host header).
Security and Performance Features
By bundling libaria2, the client handles multi-stream, resumable downloads and uploads from the terminal. For security, gdirect ignores the operating system's CA bundle and strictly verifies TLS connections against embedded Google Trust Services (GTS) roots, mitigating risk even when traversing third-party relays. Users can disable the default relay server entirely using --google-only.
Target Audience and Maturity
Licensed under GPL-2.0 with over 750 GitHub stars, gdirect is tailored for technical users operating under strict network filtering. The project demonstrates a well-architected approach to censorship circumvention, though the longevity of its bypass mechanisms depends on ongoing firewall heuristics.