diff --git a/disclaimer/index.html b/disclaimer/index.html index c8760fa..10962f0 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 fafd27a..3c77c88 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 b988be7..8007697 100644 --- a/faq/index.html +++ b/faq/index.html @@ -21,7 +21,7 @@ - + @@ -31,23 +31,23 @@ - + - + - - + + - - + + @@ -63,8 +63,8 @@You should contact with your provider to double check if there is interest in being added to Passepartout. Beware that some may be concerned instead. Ultimately, you can submit your provider request for a viability review to providers@passepartoutvpn.app.
-UPDATE: due to user demands and broader compatibility, today Passepartout does support compression, but LZO only. Both --comp-lzo [yes]
and --compress lzo
are now legal options. Other algorithms (e.g. LZ4) are not supported and never will. All in all, the use of compression is still discouraged.
~
- -Some users may have noticed that Passepartout is was not compatible with any compression algorithm supported by OpenVPN. This is was intentional and comes came from a logical reasoning. Besides being a relevant overhead against marginal gains -most protocols in the application layer (e.g. HTTP) already use compression nowadays-, compression is vulnerable to an attack that may be able to reveal the secret session keys.
The attack is called VORACLE and is extensively explained by the very authors of OpenVPN. Most major providers have taken action and fixed the issue, but many are still refraining to disable compression for no acceptable reason. In case this happens, you are warmly encouraged to report the issue immediately and possibly link to either the official resource you find above, as it comes directly from the software makers, or this page.
- -BEWARE: it’s not about making the app work, this is about your safety. Do prompt your provider to disable compression ASAP. Most of the time it’s as easy as tweaking a single configuration line on their backends.
- -Keeping it broken is absolutely irresponsible.
-The Wi-Fi/LTE icon (replace LTE with any cellular signal) while on VPN has been broken since iOS 10 or the like. It’s something that Apple is unable to fix or doesn’t bother fixing.
@@ -100,6 +86,12 @@I haven’t found a workaround for this and it’s been there for almost two years. Yeah, it’s a shame.
+Starting from iOS 12 (or 13?), iOS has somewhat restricted what apps can learn about Wi-Fi networks. The effect of this is the inability to add the connected Wi-Fi network to trusted networks, be it with a bogus “Wi-Fi” or “WLAN” SSID name, or with the alert “You are not connected to any Wi-Fi network.”.
+ +To work around this issue, you should trust the network while the VPN is enabled and connected through such network. I will try to restore former behavior in future versions of Passepartout, or at least add an informational footer below the “Trusted networks” section.
+Due to easier interoperability, the app does not support external files in the .ovpn main configuration. That’s because more often than not, it may not make sense referring to relative paths in a mobile device environment. Think of the Mail app for example. The fix is straightforward though, say you have an external ca
file: