On Encryption
privateinternetaccess.com
On Encryption
1–10 of 21 posts
Re: On Encryption
#2Re: On Encryption
#3[deleted]
Re: On Encryption
#4Re: On Encryption
#5[deleted]
For OpenVPN - which is the only protocol we advise for real security (PPTP and IPSec/L2TP are fine for just hiding your IP) - we don't use pre-shared keys. OpenVPN uses TLS for exchanging strong symmetric keys. Your password is only used for authentication and its entropy isn't related to your session's security.
Re: On Encryption
#6I would not make the assumption that 1024 bit conventional Diffie Hellman is safe.
Re: On Encryption
#7I would not make the assumption that 1024 bit conventional Diffie Hellman is safe.
You're probably right. We've already changed to 2048 DH everywhere. Do you have any opinion on if that is a strong enough default?
[1] http://www.openssl.org/docs/apps/ecparam.html
[2] https://github.com/polarssl/polarssl/commit/577e006c2fe4a361...
Re: On Encryption
#8Re: On Encryption
#9Earlier quoted context omitted.
You're probably right. We've already changed to 2048 DH everywhere. Do you have any opinion on if that is a strong enough default?
Does OpenVPN support ECDH parameters yet? openssl supports ecparam[1], and polarssl is now supporting it in their development branch[2]. [1] http://www.openssl.org/docs/apps/ecparam.html [2] https://github.com/polarssl/polarssl/commit/577e006c2fe4a361...
Re: On Encryption
#10 > 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...