[1] http://www.openssl.org/docs/apps/ecparam.html
[2] https://github.com/polarssl/polarssl/commit/577e006c2fe4a361...
> We will also be adding support for something no other provider is currently offering called Elliptic Curve Cryptographic security, with both 256bit and 521bit curves.
Any particular reason to not offer 384bit as well?ps. likely a typo: 521 should be 512?
edit: Nope. 521 is correct[1]. thanks @mtoledo
[1]: https://en.wikipedia.org/wiki/Elliptic_curve_cryptography#ci...
https://en.wikipedia.org/wiki/Elliptic_curve_cryptography#ci...
They provide a perfect honeypot to gather the "illegal" web users or those with something to hide, in one place.
Then it is fairly simple to start pattern matching the unencrypted traffic exiting your endpoints by matching HTTP headers for each client. Then all they would need is for a VPN user to acces a website that leaks the user's identity and you can back match their previous traffic.
For example, you search for information on "how to make a bomb" via the VPN. Your browser sends the the HTTP headers, Accept-Language set to Accept-Language: ar-YE,en-US,fr-FR,de-DE;q=0.5 and a user agent of Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:21.0.0) Gecko/20121011 Firefox/21.0.0. Those HTTP headers aren't unique, but they vastly narrow the search scope.
Now as that user you visit your Facebook page, and those same matching HTTP headers are passed. Boom, you've just leaked your true identity.