summaryrefslogtreecommitdiff
path: root/app/assets/urls
AgeCommit message (Collapse)Author
2016-09-19Remove pins (solves #8455)kwadronaut
remove pins, because didn\'t work this way (solves #8455)
2015-06-08s/buildtype/flavor, changed riseup's pinParménides GV
Riseup's EE certificate expired (EE = End-Entity, the commercial certificate signed by the issuer), and we weren't able to fetch provider.json because the pin wasn't valid. This problem needs to be avoided in the future, using HKPK (https://tools.ietf.org/html/rfc7469), which Micah's implementing on Riseup. Switching from build types from flavors enables us to run tests against production apk, not just debug. I didn't detect this pinning problem because tests were run only against the debug apk, which trusted preseeded providers by default (thus bypassing pinning issue).
2015-04-22Pinning connection to provider.jsonParménides GV
Using AndroidPinning library from Moxie, I make sure the provider.json file Bitmask downloads is fetched from a pinned https connection, so that the api certificate fingerprint is the good one.
2014-12-15Calyx and Riseup are preseeded providers.Parménides GV
2014-04-09Back to the standard "app" module.Parménides GV
This return to "app" instead of "bitmask_android" is due to this reading: https://developer.android.com/sdk/installing/studio-build.html#projectStructure I'll have to tweak the final apk name in build.gradle.
2014-04-08Rename app->bitmask_androidParménides GV
This way, gradle commands generate apks correctly named.
2014-04-08Compiles correctly: app/build-native + gradle.Parménides GV