Add traffic obfuscation options!
Tools can use pluggable libraries traffic obfuscation which all work using a unified system that disguise traffic to be more resilient against DPI and IP based censorship. Some VPNs offer this already, and it's pretty awesome. The Tor Project maintains the spec, but it doesn't require the traffic to use Tor: https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports
Anonymous
shared this idea
Interesting idea.
We already offer obfuscation via our Chameleon protocol. Are you looking for user-configurable options?
2 comments
-
Anonymous
commented
(It could also be an option for your non pro/premier tiers, with Chameleon as your high-end solution, but still with other PTs as fallbacks. Also, with iOS9, The Guardian Project team is adapting this for the new VPN options, so it can work on both Android (https://github.com/guardianproject/pluto) and iOS (forthcoming)
-
Anonymous
commented
Kinda - more like, having multiple backups. Might be easier if the user doesn't usually see the options (maybe via an advanced configuration option). In the case where Chameleon becomes blocked, having an (automatic?) failover to other options which could be a mix of the community-supported ones (like obfs4 and meek) as well as other proprietary backup options seems like a cool idea, and useful to provide additional uptime for users while updating Chameleon?