Нема описа

Rod Hynes 5aaeeb93ba Use an explicit stop signal to gracefully stop HTTP proxy without spurious error message пре 11 година
AndroidApp 42eaaf26a3 README updates пре 11 година
psiphon 5aaeeb93ba Use an explicit stop signal to gracefully stop HTTP proxy without spurious error message пре 11 година
.gitignore 713c12cfa2 Added config and db files to gitignore пре 11 година
LICENSE 878ccd5658 initial version пре 11 година
README.md ecfb147ba3 Added support for upstream HTTP proxy; fix missing BindToDevice support for fetch remote server list пре 11 година
psiphonClient.go 7c62e96ae4 Add graceful shutdown to psiphonClient; move log file initialization out of the "library" package as log.SetOutput has global effect пре 11 година

README.md

Psiphon 3 Tunnel Core README

Overview

A Psiphon client component implemented in Go. This component provide core tunnel functionality, handling all aspects of connecting to Psiphon servers and relaying traffic through those servers. Local proxies provide an interface for routing traffic through the tunnel.

This component does not include a UI and does not handle capturing or routing local traffic. These major aspects are handled by other parts of Psiphon client applications.

Status

This project is currently at the proof-of-concept stage. Current production Psiphon client code is available at our Psiphon 3 repository.

Setup

  • Go 1.3 (or higher) is required.
  • In this repository, run go build to make the psiphon-tunnel-core binary.
  • Note that the psiphon package is imported using the absolute path github.com/Psiphon-Labs/psiphon-tunnel-core/psiphon; without further local configuration, go will use this version of the code and not the local copy in the repository.
  • This project builds and runs on recent versions of Windows, Linux, and Mac OS X.
  • Run ./psiphon-tunnel-core --config psiphon.config where the config file looks like this:

    {
        "PropagationChannelId" : "<placeholder>",
        "SponsorId" : "<placeholder>",
        "RemoteServerListUrl" : "<placeholder>",
        "RemoteServerListSignaturePublicKey" : "<placeholder>",
        "LogFilename" : "",
        "LocalHttpProxyPort" : 0,
        "LocalSocksProxyPort" : 0,
        "EgressRegion" : "",
        "TunnelProtocol" : "",
        "ConnectionWorkerPoolSize" : 10,
        "TunnelPoolSize" : 1,
        "PortForwardFailureThreshold" : 10,
        "UpstreamHttpProxyAddress" : ""
    }
    
  • Replace each <placeholder> with a value from your Psiphon network. The Psiphon server-side stack is open source and can be found in our Psiphon 3 repository. If you would like to use the Psiphon Inc. network, contact developer-support@psiphon.ca.

  • The project builds and runs on Android. At this time, Android support is in the developer branch of Go, so build Go from source and use the Android NDK to build android/arm target support. See the sample AndroidApp README for more information about building the Go binary, along with a sample Android app that uses it.

Roadmap

TODO (short-term)

  • requirements for integrating with Windows client
    • split tunnel support
    • implement page view and bytes transferred stats
    • resumable download of client upgrades
  • Android app
    • open home pages
    • Go binary PIE, or use a Go library and JNI
    • settings UI (e.g., region selection)
  • sometimes fails to promptly detect loss of connection after device sleep
  • PendingConns: is interrupting connection establishment worth the extra code complexity?
  • log noise: "use of closed network connection"
  • log noise(?): 'Unsolicited response received on idle HTTP channel starting with "H"'

TODO (future)

  • meek enhancements
  • SSH compression
  • preemptive reconnect functionality
    • unfronted meek almost makes this obsolete, since meek sessions survive underlying HTTP transport socket disconnects. The client could prefer unfronted meek protocol when handshake returns a preemptive_reconnect_lifetime_milliseconds.
    • could also be accomplished with TunnelPoolSize > 1 and staggaring the establishment times
  • implement local traffic stats (e.g., to display bytes sent/received)
  • more formal control interface (w/ event messages)?
  • support upgrading core only
  • try multiple protocols for each server (currently only tries one protocol per server)
  • support a config pushed by the network
    • server can push preferred/optimized settings; client should prefer over defaults
    • e.g., etablish worker pool size; tunnel pool size

Licensing

Please see the LICENSE file.

Contacts

For more information on Psiphon Inc, please visit our web site at:

www.psiphon.ca