bitmask_android.git - [bitmask

Age	Commit message (Collapse)	Author
2018-08-17	#8896 move preconfigured providers to flavor normal and custom	cyBerta

2018-02-21	#8858 add custom providers to the providers list on successful setup	cyBerta

2018-01-03	8773 add provider details for preseeded providers	cyBerta

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

2014-04-09	Back 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.
2014-04-08	Rename app->bitmask_android	Parménides GV
	This way, gradle commands generate apks correctly named.
2014-04-08	Compiles correctly: app/build-native + gradle.	Parménides GV