![]() ![]() When using a GCM cipher (the default in the Desktop and iOS application), data authentication is provided as part of the GCM construction itself. Using the Data Authentication setting is only relevant when using a CBC cipher. We will use the most secure option going forward. With that being said, we will be eliminating the Data Authentication and Handshake settings, as they are no longer as relevant as they were when the patches were introduced. However, OpenVPN 2.4 and later supports cipher negotiation as a standard feature, which supersedes most of the functionality of the PIA patches. These specific PIA patches were originally created to allow our users to customize the applications Encryption and Authentication settings on a per-connection basis, which was not supported by OpenVPN at the time. More responsive deployment of OpenVPN updates for future improvements and fixes Reduced risk of issues due to custom patches Handshaker phone settings manual#Improved compatibility with manual connections The elimination of these patches will allow us to provide our users with several benefits, such as: ![]() Motivation:Īs previously stated, we are eliminating PIA-specific patches to OpenVPN on both Desktop and Mobile PIA applications. RAS2048, RSA3072, RSA4096, ECC-256k1, ECC-256r1, ECC-521Īdditionally, the Data Encryption choice of “None” will no longer be available (other settings will still be supported). ![]() (CBC or no encryption): SHA1, SHA256, None In preparation for this migration, we will be removing some settings within our Desktop and Mobile applications that will no longer be supported. In order to continue to provide PIA users with an application that provides the best stable connection to the VPN, PIA has decided to eliminate PIA-specific patches to OpenVPN. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |