| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2018-01-09 | create ProviderDetail Activity | Fup Duck | |
| 2017-12-19 | adjust Fragments | Fup Duck | |
| 2017-12-07 | Rename constants | Fup Duck | |
| * renamed last constants * remove unnecessary updates/ConstantUnification | |||
| 2017-12-06 | move constants | Fup Duck | |
| * move EIPConstants to Constants * unify EIPConstants where possible * create Updater | |||
| 2017-11-24 | Add Splash StartActivity | Fup Duck | |
| * added Splash StartActivity to handle updates and initialization * created global Constants * renamed EIP Constants | |||
| 2017-11-06 | #8777 fixes NPEs and errorneous provider selection | cyBerta | |
| 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). | |||
 |
index : bitmask_android.git | |
| [bitmask_android] | git repository hosting |
| summaryrefslogtreecommitdiff |