summaryrefslogtreecommitdiff
path: root/app/src/production/java/se/leap/bitmaskclient/ConfigurationWizard.java
AgeCommit message (Collapse)Author
2018-01-27fix comments for mergerequestFup Duck
2018-01-27fix first comments on merge requestFup Duck
2018-01-19improve layoutFup Duck
* improve layout * gracefully handle orientation changes * respect small devices * set correct colors for buttons, error messages...
2018-01-16resolve commented issuesFup Duck
* recreate activity correctly after changing orientation * replace getApplicationActivity
2018-01-13rename variables to CamelCaseFup Duck
2018-01-048773 preseeded providers implementation for insecure flavorcyBerta
2018-01-038773 preseeded providers implementation for production flavorcyBerta
2017-11-06reduce duplicate code in ConfigurationWizard for different flavorscyBerta
2017-11-06#8777 fixes NPEs and errorneous provider selectioncyBerta
2017-10-31#8757 new ProviderApiBase includes commonly used code between different ↵cyBerta
implementations of ProviderAPI
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).