| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2016-09-19 | Remove pins (solves #8455) | kwadronaut | |
| remove pins, because didn\'t work this way (solves #8455) | |||
| 2015-06-08 | s/buildtype/flavor, changed riseup's pin | Parmé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-22 | Pinning connection to provider.json | Parmé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-15 | Calyx and Riseup are preseeded providers. | Parménides GV | |
 |
index : bitmask_android.git | |
| [bitmask_android] | git repository hosting |
| summaryrefslogtreecommitdiff |