leap_android.git/assets/urls, branch master [leap_android] User messages are now in string.xml 2013-06-20T14:53:14+00:00 Parménides GV parmegv@sdf.org 2013-06-20T14:52:43+00:00 f4956bb818fb9ed04760e6de3b53b876272da5cc Some more constants added to ConfigHelper. This solves #2908. 
Some more constants added to ConfigHelper.

This solves #2908.
bitmask json files are downloaded. 2013-06-13T15:37:37+00:00 Parménides GV parmegv@sdf.org 2013-06-13T15:37:37+00:00 30c7bab5d8618df665e602fdd08bafa010a15497 There was a problem on the assets file "bitmask.url". It had an error in the eip-service url. We should use this file only for main url, and proceed as if it were a new provider but with a preseeded main url. 
There was a problem on the assets file "bitmask.url". It had an error in
the eip-service url.

We should use this file only for main url, and proceed as if it were a
new provider but with a preseeded main url.
 "Trust completely" checkbox saves that trust for the new provider 2013-04-29T15:09:12+00:00 Parménides GV parmegv@sdf.org 2013-04-24T18:01:28+00:00 69389ee7db23ce7182b21da08d227d88d6cfdc46 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. 
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.
 Resolved issue: 2013-02-26T17:27:01+00:00 Parménides GV parmegv@sdf.org 2013-02-26T17:27:01+00:00 a8274e8b2649481f22bfc6d205d2ca7599fea065 Change bitmask eip-service.json url from api/1 to api:4430 (Support #1759) 
Change bitmask eip-service.json url from api/1 to api:4430 (Support
#1759)
 Simplified certificates and urls: only 1 certificate, and no :443 port 2013-02-05T19:46:33+00:00 Parménides GV parmegv@sdf.org 2013-02-05T19:46:33+00:00 1d5f1c320ee67cfadd62aeef056a043bee75096d in eip. Downloads certificate and eip from web, and loads provider from assets. KeyStore not created with latest version of BouncyCastle. Looking forward to file a bug and look for a solution. 
in eip.

Downloads certificate and eip from web, and loads provider from assets.

KeyStore not created with latest version of BouncyCastle. Looking
forward to file a bug and look for a solution.
 Problems with downloaded file, the emulator cannot find the file 2013-01-31T21:12:21+00:00 Parménides GV parmegv@sdf.org 2013-01-31T21:12:21+00:00 92c32b0b96938009af55ed28920472f22a4614ee downloaded. Seen http://code.google.com/p/android/issues/detail?id=18462 and decided to look for another solution. First solution thought (and going to be the next test): HTTP Get request :) 
downloaded.

Seen http://code.google.com/p/android/issues/detail?id=18462 and decided
to look for another solution.

First solution thought (and going to be the next test): HTTP Get request
:)