bitmask_android.git - [bitmask

Age	Commit message (Collapse)	Author
2018-01-04	8773 preseeded providers implementation for insecure flavor	cyBerta

2017-12-12	Add Splash StartActivity	Fup Duck
	* added Splash StartActivity to handle updates and initialization * created global Constants * move EIPConstants to Constants * create update possibility * use VectorDrawable as background for StartActivity
2017-11-09	Merge branch '8777_crashes_when_clicking_too_fast' into 'master'	cyberta
	8777 crashes when clicking too fast See merge request leap/bitmask_android!16
2017-11-06	reduce duplicate code in ConfigurationWizard for different flavors	cyBerta

2017-11-06	#8777 fixes NPEs and errorneous provider selection	cyBerta

2017-11-03	#8778 fixes invalid provider error handling	cyBerta

2017-10-31	#8757 new ProviderApiBase includes commonly used code between different ↵	cyBerta
	implementations of ProviderAPI
2017-10-29	add missing import...	cyBerta

2017-10-29	#8757 refactores ProviderAPI for production flavor	cyBerta

2017-10-28	#8757 refactores ProviderAPI for insecure flavor, fixes tests, renames ↵	cyBerta
	confusing constants, updates robotium
2017-10-25	8757 fixes session cookie handling by implementing okHttpClient and custom ↵	cyBerta
	cookiejar, enables TLS 1.2 on old devices, restricts allowed cipher suites on new devices in order to harden tls based communication
2017-09-21	update ics-openvpn: update classes, manifest, resources and build script	cyBerta

2016-02-06	Update build tools and compile sdk version.	Parménides GV
	Warn about the needed libraries for 64 bit systems.
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).