Skip to content

Latest commit

 

History

6 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

Github-direct

English | 简体中文

Latest release Source LSPosed API

This is the LSPosed distribution repository for Github-direct. The complete source code, technical documentation, and issue tracker live at FxxkLocation/Github-direct.

Github-direct is a selective network-connectivity module for Android Root and LSPosed environments. It combines pollution-resistant DNS, verified endpoint candidates, transparent TCP/TLS relaying, and fail-open protection, and operates only on applications explicitly selected by the user.

GitHub is the stable baseline with completed end-to-end device validation. Google, YouTube, Discord, and OpenAI / ChatGPT profiles remain experimental, are disabled by default, and require separate validation on each device and network.

Highlights

  • LibXposed API 102 with minimum compatibility at API 101.
  • LSPosed hooks and the Root data plane require separate authorization; an empty scope never expands to the whole device.
  • The transparent Root backend dynamically probes su, iptables, owner matching, REDIRECT, and optional IPv6 capabilities.
  • Endpoint candidates must pass TCP, public certificate-chain, real-hostname, and endpoint-semantic verification.
  • Capability, listener, rule-installation, or health-check failures automatically remove this module's rules and restore the native path.
  • Supports arm64-v8a, armeabi-v7a, x86_64, and 16 KiB ELF LOAD alignment.

Requirements

  • Android 8.0+ (API 26)
  • LSPosed or another framework compatible with modern API 101+
  • Magisk / KernelSU with working su and iptables for Root transparent mode
  • Complete ip6tables and listener capability checks for IPv6 interception

Installation

  1. Download the APK from this repository's Releases.
  2. Enable the module in LSPosed and select only the target applications that need it.
  3. Open Github-direct, grant Root access, and select the same applications in the in-app Root scope.
  4. Start the service and confirm that the status page shows an active rule generation and no failure stage.

The normal path does not require a CA. Browser TLS termination is limited to hosts explicitly authorized a second time and requires a per-device CA, strict upstream certificate and hostname validation, and controlled suffix boundaries. Certificate-pinned native clients are not guaranteed to work.

Current release

1.1.1 (versionCode 3) fixes a compatibility issue where some legacy/nft iptables -S implementations reorder rule arguments and caused the Root backend to report installed rules as missing. Startup verification and runtime health checks now compare the chain, UID, destination, protocol, port, and jump target semantically, without model- or vendor-specific branches.

Downloads and source

APK SHA-256: d4b372925751fbed2c128a2c14991bcf276750a5b26344621bbf63e5cdc8c330

Releases

Packages

Contributors