summaryrefslogtreecommitdiff
path: root/assets
diff options
context:
space:
mode:
authorParménides GV <parmegv@sdf.org>2013-04-24 20:01:28 +0200
committerParménides GV <parmegv@sdf.org>2013-04-29 17:09:12 +0200
commit69389ee7db23ce7182b21da08d227d88d6cfdc46 (patch)
treeb521f6c8b86a153b3a126af4ff28b78283de7e84 /assets
parentbfe2263d6b73159a4f929bc7b1fdeb724c88e8de (diff)
"Trust completely" checkbox saves that trust for the new provider
entered, so that if in the future the client tries to log in or whatever, it can use the certificate downloaded when added. Log in dialog works ok, showing a toast when authentication fails (by this time, I have not managed to get a correct login due to dev.bitmask.net problems). dev.bitmask.net works perfectly, via adding it as a new provider (MeanderingCode, this is for you ;) ). All GET requests are done by default Android URL class, which means that certificates trusted by Android are also trusted by us. If there are problems when logging in due to certificates, the app is able to use only the certificate associated to the provider in the moment it was selected as the chosen provider.
Diffstat (limited to 'assets')
-rw-r--r--assets/urls/bitmask.url3
1 files changed, 2 insertions, 1 deletions
diff --git a/assets/urls/bitmask.url b/assets/urls/bitmask.url
index 910f0400..bc4d59db 100644
--- a/assets/urls/bitmask.url
+++ b/assets/urls/bitmask.url
@@ -3,5 +3,6 @@
"assets_json_provider" : "providers/bitmask.net_provider.json",
"json_provider" : "https://bitmask.net/provider.json",
"cert" : "https://bitmask.net/ca.crt",
- "json_eip_service" : "https://api.bitmask.net:4430/1/config/eip-service.json"
+ "json_eip_service_antiguo" : "https://api.bitmask.net:4430/1/config/eip-service.json",
+ "json_eip_service" : "https://api.bitmask.net:4430/config/eip-service.json"
} \ No newline at end of file