Age | Commit message (Collapse) | Author |
|
Next step: understand why SHA-256 digest from NG_1024 is not equals to
the one leap_web is calculating.
|
|
Cleaned some code, pending the M2 one (testing with M1).
|
|
M1 is not OK, because errors (with null description, awkward) are
received from posting M1 to the server instead of M2.
Next step: purge user database from leap_webapp and start testing again.
|
|
Refactored downloadJsonFiles in ProviderAPI, new method from block in
the intent identification.
|
|
Next step: get cookies understood, how do I get server's sent
parameters?
|
|
Next steps:
Implement async communication with the server to receive salt, send A
and receive B.
|
|
ProviderListFragment, and then the user can choose it.
|
|
the website, just as bitmask.net/provider.json), and writes it to a file
in ~/leap_android.
Next steps: parse that file and download eip-service and cert.
|
|
|
|
Moves towards our wizard flow; Addresses #1497 #1500
|
|
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.
|
|
and bitmask.net.
Both prefs are downloaded and parsed to SharedPreferences.
|
|
the saveSharedPrefs method and an unimplemented rescueFromJSONException.
Next step: managing HttpsURLConnection for the
CertPathValidatorException.
|