ics-openvpn VS session-android

When I am trying to build https://github.com/schwabe/ics-openvpn > main. I am constantly get the following error:

I've been working for a few days to build a good working VPN app (Non-commercial) but I'm finding so many different implementations of https://github.com/schwabe/ics-openvpn that I don't know exactly where to start.

OpenVPN for Android (version 0.7.46): OpenVPN without root

You could ask upstream: https://github.com/schwabe/ics-openvpn (also, is that the app you're using?)

Just the android phone with Openvpn for Android (https://github.com/schwabe/ics-openvpn) thinks that it's too good for a new dns lookup, takes the ip it has cached from the previous connection and therefore can't connect. It retries until i manually disconnect and reconnect it. Only then a new dns lookup happens and it gets the current ip to then connect without a problem.

For the Android app it lists: https://github.com/schwabe/ics-openvpn

I know that Apple limits what you're permitted to install on their phones, but perhaps there's another openvpn version that has this feature that you're permitted to use. In case it can help, the version I'm using seems to be from https://github.com/schwabe/ics-openvpn/ . Perhaps someone has done something similar for Apple phones.

I've been looking into doing something similar and stumbled upon a method that uses personalDNSfilter with OpenVPN for personalDNSfilter, which is a special version of the OpenVPN for Android app.

In addition we back several other open source projects, such as the OpenVPN GUI, OpenVPN for Android and OpenVPN 3 Linux ... these all provide various user interfaces on top of the OpenVPN Core component.

OpenVPN for Android (version 0.7.37): OpenVPN without root

Other alternatives include Session (free) and Threema (paid - 5€).

Test it by downloading session at getsession.org and DM the bot by starting a new message and sending it to “Simple” (without quotes)

Figured there should be moves to set one up if not - https://getsession.org/

* marketing "Perfect Forward Secrecy" AKA "Forward Secrecy"[0].

I favor Session Private Messenger[1] because it is decentralized and allows third party clients, but Signal enthusiasts warn me that the Session client may, hypothetically, at some future date, integrate a cryptocurrency, as the Signal client already does[2].

[0] https://en.wikipedia.org/wiki/Forward_secrecy

[1] https://getsession.org

[2] https://www.stephendiehl.com/blog/signal.html

If you have a mobile phone number, the domestic intelligence agency knows exactly where you are at all times and any LEO (without a warrant) can also find you. In addition, there have been numerous CCC presentations showing how insecure the global (excluding US) and (separately) US carriers are guilty of promiscuous metadata trafficking ($$) and insecure SS7 setups. As a consequence, for low $, you can go to any one of several shady websites and find the last location of almost any phone number (person unique ID) globally. There are additional varying exploitable vulnerabilities depending on the exact combination of {handset x carrier x country} to impersonate them, tap their line, reveal their exact location, and redirect their phone number through a third-party handset or even a PBX. These are more expensive and some capabilities are forbidden for all but a few selective intelligence uses.

Session (Signal fork) doesn't use phone numbers. It's pretty well-designed overall and uses an onion routing approach. It's already a superset of Signal except it doesn't use phone numbers. https://getsession.org

Also look interesting:

* (unproven) https://www.olvid.io/technology

* (unproven) https://simplex.chat

PS: Using regular TOR on home broadband or cloud servers is relatively risky and inefficient. Sybil attacks on it are common. And to network operators and security agencies it gives an easy "flow tag" of your uplink and exit node data traffic as automatically suspicious.