Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-01-19 | improve layout | Fup Duck | |
* improve layout * gracefully handle orientation changes * respect small devices * set correct colors for buttons, error messages... | |||
2018-01-16 | resolve commented issues | Fup Duck | |
* recreate activity correctly after changing orientation * replace getApplicationActivity | |||
2018-01-13 | rename variables to CamelCase | Fup Duck | |
2018-01-04 | 8773 preseeded providers implementation for insecure flavor | cyBerta | |
2018-01-03 | 8773 preseeded providers implementation for production flavor | cyBerta | |
2017-11-06 | reduce duplicate code in ConfigurationWizard for different flavors | cyBerta | |
2017-11-06 | #8777 fixes NPEs and errorneous provider selection | cyBerta | |
2017-10-31 | #8757 new ProviderApiBase includes commonly used code between different ↵ | cyBerta | |
implementations of ProviderAPI | |||
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). |