strongSwan VPN Client for Android 4+¶
- Table of contents
- strongSwan VPN Client for Android 4+
Client certificates and keys, and CA certificates may be added by bundling them into a PKCS#12 file and then importing that file into the Android system keystore. CA certificates and server certificates may also be imported directly into the app since 1.4.0. Importing CA certificates into the Android system keystore may trigger a warning since Android 4.4 (Network may be monitored by an unknown third party), whereas importing CA certificates directly into the app will work fine.
Since 1.9.0 split tunneling may be configured on the client (i.e. to only route specific traffic via VPN and/or to exclude certain traffic from the VPN). The client always proposes 0.0.0.0/0 as remote traffic selector and narrowing performed by the server still applies. Since 1.5.0 the user may opt to block all traffic not destined for the VPN if the server does narrow the traffic selector or split tunneling is configured on the client.
Since 1.9.0 it is possible to limit a VPN connection to specific apps or exclude certain apps from using the VPN (to them it will seem as if no VPN is present).
Since 2.0.0 an optional Quick Settings tile (Android 7+) shows the current connection status and allows connecting/terminating the current VPN connection easily. The same version brought support for the Always-on VPN feature that may be enabled in the system's VPN settings on Android 7+ and will start the VPN profile after a reboot (refer to the changelog for potential caveats). The default VPN profile used for these two features may be configured in the app's global settings (the default is to initiate the most recently used profile).
The app allows creating shortcuts on the Android Launcher to quickly initiate specific VPN profiles.
Since 2.0.0 it's possible to use Intents and a VPN profile's UUID to connect/terminate it with automation apps such as Llama or Tasker e.g. based on location, WiFi hotspots or other events.
The app is compatible to the Windows example configurations we provide (although the app supports stronger algorithms than Windows clients do) and the IKEv2 roadwarrrior examples. Since strongSwan 5.2.1 and version 1.4.5 of the app fragmentation=yes may be added to the server config to use IKEv2 fragmentation, which avoids problems with IP fragmentation during connection establishment (due to large certificates or lots of certificate requests).
Important: The hostname/IP of the VPN server, as configured in the VPN profile, has to be contained as subjectAltName extension in the VPN server's certificate. Since 1.6.0 the server identity may also be configured explicitly.
- Only IKEv2 is supported
- Client authentication is limited to:
- EAP authentication based on username/password (EAP-MSCHAPv2, EAP-MD5, EAP-GTC)
- RSA/ECDSA authentication with private key/certificate
- EAP-TLS with private key/certificate (see 1.4.5 for limitations)
- The server always has to be authenticated with RSA/ECDSA (even when using EAP-TLS, see 1.4.5)
- PSK authentication is not supported, as it is potentially very dangerous because the client might send the hash of a weak password to a rogue VPN server. Thus we prefer EAP authentication where the server is first authenticated with a certificate and only afterwards the client uses its password.
- Only a single tunnel can be established at a time
- The IPsec default proposals are limited to AES encryption with SHA2/SHA1 data integrity or AES-GCM authenticated encryption. Optionally, using PFS with one of a number of proposed ECP/MODP DH groups. Since 1.7.0 ChaCha20/Poly1305 authenticated encryption and Curve25519-based DH is also supported and proposed. And since 1.9.5 a custom ESP proposal may be configured.
- The app is not compatible with Google's Project Fi, which provides its own always-on VPN connection. To use the app this has to be disabled first using the following procedure.
- If you don't get a list of installed apps to exclude/include from the VPN you might have to explicitly allow the strongSwan app to get this list. For instance, on the Huawei Mate 9 via Phone Manager > Permissions.
- It might be necessary to exclude the app from any battery saver feature on the system (e.g. on the Xiaomi MIUI8).
- Apps that create a screen overlay, such as Twilight or Night Mode, might interfere with the dialog to grant the app permission to create a VPN connection (unable to tap OK/Grant). If that's the case, temporarily disable any such app or, if possible, whitelist/exclude the VPNDialogs system app from this feature.
- Note: There are some serious issues on Android 4.4 before 4.4.3 (see #462)
- If you have problems with the app, find bugs or have feature requests you may open a new issue report (please use the search function first to avoid duplicates). You may also send us the log file via email directly from within the app.
Sometimes we publish beta versions of our app on Google Play. If you'd like to try new features and provide us with valuable feedback, please opt-in here, or directly from the app's page in the Play store.
- Authentication via EAP-MSCHPv2 now supports UTF-8 encoded passwords
- Fixes an issue with upgrades from older versions
- Adds a copy command to duplicate an existing VPN profile
- Allows configuring custom DNS servers for each VPN profile
- Fixes potential DNS leaks caused by a bug in Android 9
- Fixes clicking some buttons (certificate selection, app selection) with keyboard navigation (also affects e.g. Fire TV sticks) when running on Android < 8
- Fixes an issue with the QuickSettings tile on some devices where the callback is called even if no tile is available
- Fixes profile selection/edit when the device is rotated
- Removes support for EAP-PEAP/TTLS as it caused major issues with commercial VPN services (one issue was that the server identity was initially enforced as AAA identity, but changing that revealed that some providers use self-signed AAA server certificates - not sure what clients accept that), hopefully proper support can be added in a future version
- Fixes a possible crash related to Android 8's optional Autofill feature (the bug that causes it was apparently fixed with Android 8.1, but has not been backported)
- Supports the Always-on VPN feature on Android 7+ (#2179)
- Android 8 only starts the VPN service after the user has unlocked the device after a reboot
- Android 7 immediately starts the VPN service after booting, but that means the app has no access to the KeyChain yet (if certificates are used), so no VPN connection can be established until the user unlocks the device
- If password authentication is used and the password is not stored in the profile, the connection is aborted and the user has to manually retry connecting to enter the password
- The "Block connections without VPN" system option on Android 8+ blocks all traffic not sent via VPN without considering any subnets/apps that are excluded from a VPN (i.e. that feature is not compatible with split-tunneling)
- Adds a Quick Settings tile on Android 7+ to quickly initiate/terminate the VPN connection (#2398)
- Similar to the Always-on feature, Android 8 doesn't enable the Quick Settings tile until the user unlocked the device after a reboot
- Disconnecting via tile from the lock screen requires the user to unlock the device, connecting is possible without (unless a password has to be entered)
- The new settings activity allows specifying a default VPN profile used for the two features above (the default is to initiate the most recently used profile)
- The app automatically tries to reconnect the VPN profile if fatal errors occur (e.g. authentication failures). The retries are delayed by an exponential backoff, which is currently capped at 2 minutes
- The status screen in the main activity as well as the notification show a countdown until the next automatic retry, manually retrying is possible from both locations
- On Android 5+ a dummy VPN interface is installed while connecting to a VPN profile, or recovering from errors, to block unencrypted traffic, while taking excluded subnets/apps configured in the profile into account
- Note that this VPN interface is removed when the VPN is disconnected
- Errors are not shown in a modal dialog anymore in the main activity, but in a banner directly above the status information (with buttons to view the log and retry connecting)
- Uses a separate activity to initiate/terminate/retry VPN profiles, which avoids having to bring the main Activity to the foreground for these actions
- Adds options to disable OCSP/CRL fetching (e.g. if it's known the server is not available, or if CRLs are too large)
- Adds an option to enable strict revocation checking via OCSP/CRL. If enabled, the authentication will fail if the revocation status of the server certificate is unknown (e.g. because no valid CRL is available)
- Fetching OCSP/CRL can now be aborted immediately (e.g. to cancel connecting if an OCSP server is not reachable)
Basic support for EAP-TTLS/EAP-PEAP has been added (#2392)Had to be removed again with 2.0.1
- Adds an option to use PSS encoding for RSA signatures instead of the classic PKCS#1 encoding (#2367)
- The explicit ESP proposals for the deprecated Suite B have been removed
- Adds more clear error messages if permission for VPNs can't be acquired (e.g. because another app has the Always-on VPN feature enabled)
- The date/time/thread is shown in the log view if enough space is available (e.g. on tablets or even in landscape orientation on phones), it should also be more efficient when displaying large logs
- Removes the MIME-type filter when importing trusted certificates, allowing the import of certificates even if they don't have an X.509 related MIME-type set
- All VPN profiles now have a random UUID assigned (its value may be copied from the profile editor e.g. to initiate/terminate a VPN profile via explicit Intent)
- Always sends the client certificate (if applicable) instead of only after receiving a certificate request (allows servers that accept certificates from lots of CAs to avoid sending certificate requests)
- Makes the IKE and/or ESP algorithms configurable
- Removes modp1024 from the default IKEv2 proposal. If the server only allows this DH group, a custom IKE proposal has to be configured in the VPN profile
- Adds support for delta CRLs
- Fixes issues with fragmented IP packets (gh#80)
- Ensures expires are triggered for the correct IPsec SA (#2399)
- Fixes an issue with multicast addresses when using split tunneling on older Android releases (#2420)
- Does not consider a DH group mismatch as failure anymore as responder of a CHILD_SA rekeying (e7276f78aa)
- Adds support to verify server certificates via OCSP
- Caches CRLs in the app directory (#2405)
- The CRL cache may be cleared via main menu
- Adds a button to reconnect the VPN profile to the "currently connected" dialog
- Don't apply/configure app selection on Android < 5 (the API is not supported there)
- Initiator SPIs are reset when retrying while reconnecting, which might avoid issues with
- Catches some random exceptions (as seen in Play Console)
- Fixes a crash on Android <= 5
- Fixes database update when updating from app versions < 1.8.0
- Fixes a crash with pre-existing profiles
- Adds support for split-tunneling on the client (only route specific traffic via VPN and/or exclude specific traffic from the VPN)
- Adds support for per-app VPN (either allow only specific apps to use the VPN or exclude certain apps from using it)
- Sending of certificate requests may be disabled (while this allows reducing the size of the IKE_AUTH message, e.g. if fragmentation is not supported, it only works if the server also sends its certificate if it didn't receive any certificate requests)
- NAT-T keepalive interval is now configurable (#2365)
- VPN profiles may be imported via SAF and allow the configuration of the new settings
- CRLs are now fetched with a simple Android-specific HTTP/S fetcher
- Adds a disconnect button in the permanent notification (#2309)
- The log view should now be more efficient (#2148)
- Fixes the handling of backslashes in usernames
- Adds a Traditional Chinese translation
- Fixes an issue while disconnecting on certain devices (#2251)
- Adds Simplified Chinese translation
- Adds support to import VPN profiles from JSON-encoded files
- Re-adds support for the ECC Brainpool DH groups (BoringSSL doesn't provide these)
- Fixes a crash (regarding libtpmtss.so) on older Android systems
- Adds a permanent notification while connected (or connecting) that shows the current status and which allows running the VpnService instance as foreground service. This in turn should prevent Android from terminating it when low on memory.
- Supports the ChaCha20/Poly1305 AEAD and Curve25519 DH algorithms
- Properly validates entered server port and MTU values in the GUI
- Logs the installed DNS servers
- Uses BoringSSL instead of OpenSSL
- Based on strongSwan 5.5.1
- Fixes a crash when importing CA/server certificates via SAF
- Fixes an interoperability issue with Windows Server. 5.4.0 changed the order of the algorithms in the default IKE proposal. Algorithms that provide a security of less than 128-bit were moved to the end of the list. Now Windows Server 2012 R2 (in its default configuration at least) only supports modp1024. The problem is that Microsoft's IKEv2 implementation only seems to consider the first fifteen algorithms of a specific transform type in the proposal. Because strongSwan supports quite a lot of DH groups and due to the reordering modp1024 was now at position 17 in the proposal, which meant Microsoft Server rejected the IKE_SA_INIT message with a NO_PROPOSAL_CHOSEN error. This has been fixed by removing some of the weaker and rarely used DH groups from the default proposal (fae18fd201).
- Also corrects the label for the password field in the login dialog
- Based on 5.4.0, which e.g. adds support for IKEv2 redirection
- Configuration of the server identity. If it is set the identity is sent as IDr during authentication and must match the server's identity exactly (i.e. it disables loose identity matching against all subjectAltNames, see #1268)
- Selection of the client identity if certificate authentication is used (see #1403)
- GUI changes:
- Removed the progress dialogs during dis-/connecting
- Redesign of the profile editor (reordered, floating labels, helper texts, "gateway"->"server")
- Tabs in CA certificate manager have been updated (sliding tabs with ViewPager)
- Switched to the AppCompat theme (Material-like)
- Increases the NAT-T keepalive interval to 45s (#1326), no attempt to send keepalives is made anymore if there is no connectivity
- Fixed the font in the log view on Android 5+
- Native 64-bit build
- Based on 5.3.2
- Roaming between networks on Android 5 and newer has been fixed (#865)
- Adds new advanced profile settings:
- A custom MTU can be specified (currently between 1280 and 1500)
- The server port can be changed (default is 500, with a switch to 4500 - there is no switch if a custom port is set), #847
- Split tunneling can be disabled by blocking all traffic that is not destined for the VPN
- Only on Android 5 and newer will split tunneling fully work if only one address family is tunneled via VPN (#782)
- Sets the preferred language for remediation instructions to the system language
- EAP-TNC does not require a client certificate anymore
- Fixes a linker issue on Android M
- Fix for CVE-2015-4171.
- Based on 5.2.1 including improved MOBIKE handling and support for IKEv2 fragmentation
- Enables optional PFS for IPsec SAs. Proposed are cipher suites with and without DH groups, so it's up to the VPN server whether PFS is used or not.
- Adds basic support for EAP-TLS. Limitations are:
- EAP-only authentication is not allowed because the AAA identity is not configurable. So to prevent anyone with a valid certificate from impersonating the AAA server and thus the VPN server, the server is authenticated with a certificate (like we do with other authentication methods)
- It's currently not possible to select a specific CA certificate to authenticate the AAA server certificate, so it either must be issued by the same CA as that of the VPN server or automatic CA certificate selection must be enabled in the VPN profile
- Adds the ability to import CA and server certificates directly into the app. On Android 4.4+ the SAF is used to allow users to browse for certificate files (if the MIME-type is not set properly the advanced view has to be used to see all files). On older systems the files may be opened from third-party file managers
- The GUI indicates if the connection is being reestablished
- A DNS proxy resolves the VPN server's hostname while reestablishing (plaintext is blocked otherwise)
- Supports ECDSA private keys on recent Android systems (tested on Android 4.4.4)
- Based on 5.1.3 (fixes a security vulnerability)
- Links libcrypto (OpenSSL) statically
- Doesn't limit the number of packets during EAP-TTLS
- Based on 5.1.1
- Fixed issues with IV generation and padding length calculation for AES-GCM
- Removes the Vstr dependency
- Fixed a regression causing remediation instructions to pile up (EAP-TNC)
- Improved recovery after certain connectivity changes
- Added support for EAP-TNC
- Disabled listening on IPv6 because the Linux kernel currently does not support UDP encapsulation of ESP packets for IPv6
- Added support for AES-GCM
- Support for IPv6-in-IPv4 tunnels
- Uses kernel-netlink to handle interface/IP address enumeration
- Added support for combined certificate/EAP authentication (RFC 4739)
- Added Polish, Ukrainian, and Russian translations
- Fixed a race condition during reauthentication and a potential freeze while disconnecting
- Added shortcuts to VPN profiles to quickly start specific connections from the launcher
- Added a confirmation dialog if a connection is started but one is already established
- Fixed a few Android 4.2 specific issues
- Added support for MOBIKE e.g. allows switching between different interfaces (e.g. Wifi and 3G/4G)
- The app tries to keep the connection established until the user disconnects manually
- Workaround for a private key issue on Android 4.1
- Added loose ID matching: While the client expects the hostname/IP of the VPN server to be contained as subjectAltName in the certificate this allows the responder to use a different IDr than that, as long as it is confirmed by the certificate (the client does not send an IDr anymore)
- Fixed a Unicode issue when converting Java to C strings
- Added certificate authentication and fixed reauthentication