summaryrefslogtreecommitdiff
path: root/app/src/release/java/se/leap/bitmaskclient/ProviderDetailFragment.java
AgeCommit message (Collapse)Author
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-03-24ProviderDetailFragment release was bad formatedParménides GV
2015-03-24Indent everything with IntelliJParménides GV
2015-03-24Cleaned imports, use wildcards when appropriateParménides GV
2014-11-26eip package, EIP constants to interface.Parménides GV
2014-08-05Append "Sign Up" to "Log in" button.Parménides GV
It's enough to reflect the fact that the button leads to a dialog from which the user can both log in or sign up.
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.