diff --git a/disclaimer/index.html b/disclaimer/index.html index 6e94596..85c4ee4 100644 --- a/disclaimer/index.html +++ b/disclaimer/index.html @@ -21,7 +21,7 @@ - + @@ -31,23 +31,23 @@ - + - + - - + + - - + +
diff --git a/donation/index.html b/donation/index.html index b63adce..e86a21c 100644 --- a/donation/index.html +++ b/donation/index.html @@ -21,7 +21,7 @@ - + @@ -31,23 +31,23 @@ - + - + - - + + - - + + diff --git a/faq/index.html b/faq/index.html index b777bed..7622e78 100644 --- a/faq/index.html +++ b/faq/index.html @@ -21,7 +21,7 @@ - + @@ -31,23 +31,23 @@ - + - + - - + + - - + + @@ -79,7 +79,6 @@At some point, TunnelKit moved from OpenSSL to BoringSSL. The switch may disrupt older ciphersuites, thus resulting in “TLS failed” when verifying peer against the CA. Regardless of the error, you should upgrade your server certificates to a more modern standard (e.g. RSA no less than 2048-bit). Passepartout should also get past the “TLS failed” error once you perform the upgrade.
+This may happen with older ciphersuites when verifying peer against the CA. You should upgrade your server certificates to a more modern standard (e.g. RSA no less than 2048-bit).
Read the related report on GitHub.
-Passepartout is slightly different from OpenVPN Connect when it comes to DNS. Due to the ability of overriding network settings in general, Passepartout lets the user specify what DNS servers to pick without any ambiguity (“Read .ovpn”, “Pull from server” or “Manual”). On the other hand, OpenVPN Connect merges and uses both the servers defined in the .ovpn file (first) and those pushed as dhcp-option
by the VPN server (last). With this in mind, you should now understand why DNS in some networks may behave differently than the official OpenVPN clients.