| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
If the connection is being established, the key with a clock icon is
shown.
If the connection has been established, the key without the clock icon
is shown.
I've also added all some icons to more resolutions.
|
|
|
|
|
|
|
|
|
|
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.
|
|
I've also fixed another message: if a file to be downloaded is not
found, we say the entered provider isn't a LEAP provider. This is based
on the fact that if provider.json doesn't exist/contain valid
information, then the url isn't pointing to a LEAP provider.
|
|
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.
|
|
Next step: show it when an error occurs.
|
|
Location keyword on android.cfg isn't supported, EIP corresponding code
has been commented out. I think we should support it in ics-openvpn, so
that we can show the location instead of the server name.
I've updated all opensssl, openvpn, etc. subprojects from rev 813 of
ics-openvpn, and jni too.
|
|
Merged updated ics-openvpn-upstream (e7803cc8efcd1794e18b4e30a43d814c2834552d).
|
|
|
|
|
|
Refactored AndroidManifest to include launchvpn and openvpnservice.
Imported changes from ics-openvpn-upstream
|
|
Now the thread managment doesn't happen statically, but through the
binded openvpn service.
|
|
Forgot to add the menu for the log.
Now we'll strive to fix se.leap.bitmaskclient problems: first compilation, then functionality.
|
|
api folder and aidl files aren't needed for us. They are used for
external apps that want to use ics-openvpn as an already installed
package, while what we want is to avoid the installation of ics-openvpn
including it (refactored) in bitmask android.
|
|
|
|
Now we need to decide what's our relationship with LogWindow and
LaunchVPN, refactor its classes and fix ours so that we use the
currently supported methods.
|
|
|
|
I'm hardcoding their values based on the compilation errors (i.e., the
drawables referenced by de.blinkt.openvpn.core.OpenVpnService). If a new
drawable were introduced, build.gradle should be updated accordingly.
|
|
I privilege ics-openvpn translation to ours. If we need to change
something, we can introduce a new xml element without any future
compatibility problem with ics-openvpn.
|
|
|
|
WARNING: there are still compiling errors, related to BuildConfig and R
classes in de.blinkt.openvpn
|
|
imports from se.leap.bitmaskclient java files have also been updated.
WARNING: compiling errors for de.blinkt.openvpn.R, aidl.de.blinkt.openvpn.
|
|
|
|
|
|
|
|
|
|
Functionality copied to the Release build.
|
|
This has the problem of localized messages. irc log questioning:
May 8th 2014
08:12 <@parmegv> mm, I was thinking... I was rephrasing the error messages given by our api during authentication
08:13 <@parmegv> I thought why should I rephrase it and think twice
08:13 <@parmegv> so now I'm just "pretty printing" the error message given by the api
08:13 <@parmegv> but that has a problem: they aren't localized
08:14 <@parmegv> would implementing a localized version of our error messages be useful?
|
