| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Always. Previously we didn't do so if EIP hadn't been started before.
Fix a small bug introduced during latest refactoring, authentication did
not work because the final result variable wasn't assigned.
|
|
Authenticate and Register methods are now renamed and split. It's much
more readable, the new emacs-default indentation helps to that too.
|
|
|
|
ConfigHelper checks for IllegalArgumentException (trace from play
store).
EIP location code has been splitted a bit.
I'd like to extract OVPNGateway out from EIP, but that's not an easy job
and this branch is already lasting to much hehehe.
|
|
It was remaining there, with an empty layout.
|
|
|
|
Set up routes to UDP unlimited server (since openvpn hasn't finished, it
simply blocks traffic) and also DNS server to 10.41.0.1.
These values correspond to current leap_platform configuration (https://github.com/leapcode/leap_platform/blob/7bc79e68e5ca913d1d2843c48cde8f946feed09c/puppet/modules/site_openvpn/manifests/init.pp)
|
|
Fixed notifications too (forgot to do it in another branch, it's #5964).
|
|
|
|
|
|
|
|
The "commit" was missing.
|
|
|
|
|
|
When the user has already been connected to a VPN and she configured the
client to use persistent-tun, we should warn her that until the VPN
connection is again established, no traffic will flow.
|
|
Now the "Waiting for server reply" notification is shown along with
native Android's VPN notification. Next step: fix it.
|
|
|
|
For providers that don't allow anonymous eip, you have no certificate
until you log in, but the check validity method works before the log in.
|
|
|
|
|
|
|
|
I don't use the eip status receiver because it wasn't reliable on
timing: updated messages were arriving before the receiver was notifying
a new state.
Current and last ConnectionStatus is now managed at EIP.
More refactoring on the eip fragment, now there are separate methods for
setting up the UI depending on the message received.
|
|
Smaller methods, simplified logic, eip status and eip progress still
need some fixes.
|
|
We don't need an eipAutoSwitched, nor to change the state of the switch
in the updateState (this method should just update the state string,
nothing more).
Still some inconsistencies with the switch, you can turn it off and on
several times to see them.
|
|
|
|
I've also fixed a simple test that wasn't letting the suite to finish
correctly.
|
|
|
|
I've also added a check for a nullpointer when eipDefinition is
null.
|
|
I've tested autostart, on+off repeated times, and switch provider. It
works.
The ServiceConnection is managed by DisconnectVPN from ics-openvpn, it's
not useful.
|
|
This is a first step for a refactoring of the EIP class.
|
|
This way, the notification shows the city of the gateway rather than the
hostname :)
|
|
It takes for granted that the certificate is valid from the very same
date it's downloaded.
|
|
This happens when we update the openvpn certificate, in the first
connection attempt.
|
|
|
|
|
|
|
|
|
|
|
|
Now we embed the openvpn cert, the corresponding ca cert and the user
key directly from EIP, while creating a vpn profile. We leave VpnProfile untouched.
|
|
We now directly use the parseConfiguration method, translating the
eip-service.json openvpn options to a string containing the
corresponding openvpn config file lines.
|
|
We use the broadcasted eip status from ics-openvpn to know if we're
connected or not.
|
|
We don't assume ca.crt is in /ca.crt anymore, but fetch the complete url
from provider.json.
We also signup against users.json file instead of simple "users", which
worked for *.bitmask.net domains.
|
|
This happens when you've used a eip enabled provider, and then you
switch to a non eip enabled one (e.g., choosing demo.bitmask.net and
then switching to cdev.bitmask.net in their current configurations).
I've also disabled the build task dependency on updating
ics-openvpn. It's causing problems, while not fixing anything.
|
|
The active gateway cannot be null.
|
|
|
|
Disconnect uses the ics-openvpn activity, and the dialog prompting the
user to confirm the disconnection is only shown when eip is connected or
is trying to connect.
|
|
Previously, it drived the user to the LogWindow.
|
|
|
|
In case there is an error, user will not be prompted with a strange log
window, but the app will provide it if s/he really wants to see it.
|
