__group__ ticket summary component version type owner status created _changetime _description _reporter OpenVPN Connect for iOS v1.2.7 1016 iOS: OpenVPN Connect clears unsaved credentials on exit with save slider enabled OpenVPN Connect OpenVPN Connect for iOS v1.2.7 Feature Wish OpenVPN Inc. assigned 2018-02-08T04:53:45Z 2021-04-27T07:53:15Z "When attempting to enter NEW credentials for an ovpn profile, exiting or re-entering the app at any point will clear both the username and password fields. It will not matter which order the fields are populated, or if the save slider is enabled at the time of exit. The App only seems to ""Save"" on a connection attempt. I propose that the credential values get saved on exit if the Save slider is enabled. For context: I keep my credentials in a password repository, and I can only copy one value at a time. The problem is that for someone who must enter either the username or the password separately, at no point will the credentials be complete if the user needs to exit to retrieve the other value. The only way I have found to enter credentials in this way is to enter the valid password (or valid username and bogus password), attempt a connection (bad credentials). Exit, retrieve the other value, enter it, and reconnect (good credentials). rated minor for workaround, and typed it a feature request instead of a bug due to the clearing being clearly by design. " hunterx1 957 X509v3 Name Constraints cause issues with recent OpenVPN Connect versions OpenVPN Connect Bug / Defect OpenVPN Inc. assigned 2017-11-08T12:38:14Z 2021-04-27T07:53:15Z "Since the recent OpenVPN Connect update our students are unable to connect to the OpenVPN server: OpenVPN core error: mbed TLS: error parsing ca certificate: X509 - The extension tag or value is invalid: ASN1 - ASN1 tag was of an unexpected value. Testing with mbedTLS 2.6.0 on a Linux computer with mbedtls_cert_app ca_file=cacertwithdns.pem mode=file shows mbedtls_x509_crt_parse returned -0x2562 with a modified version you see that it finds an unknown critical extension and bails out. It seems that it doesn't support X509v3 Name Constraints. In my opinion OpenVPN Connect should use a modified version of mbedTLS which ignores the X509v3 Name Constraints extension as long as they aren't supported by mbedTLS (DNS checks should be handled by OpenVPN directly) and gives a warning to the user and then the option to decide whether he/she wants to connect anyway. Probably you won't see many CAs with name constraints extensions in the wild, but they are useful when you want to create your own CA and protect your users and yourself from abuse (your own CA should only be able to create certificates for your domain and should not be misused for creating certificates for other domains)." sysadmin-htlleonding 1023 "OpenVPN Connect for Android: Can't install: ""No Carrier""" OpenVPN Connect Bug / Defect OpenVPN Inc. assigned 2018-02-20T07:01:56Z 2021-04-27T07:53:15Z "Dear OpenVPN team, I tried to install OpenVPN Connect for Android from Google Play, but I'm getting ""No Carrier"" error message from Play store, so I can't even download it. My android device is an Nvidia Shield TV, and I suppose the reason why I'm getting ""No Carrier"" it is because this device doesn't have any SIM card slot. However, it is a fully functional device with wired/wifi network interfaces. Would it be possible to remove ""No Carrier"" restriction in future releases of OpenVPN Connect? Thanks & best regards, Andris " bandipapa