summaryrefslogtreecommitdiff
path: root/app/src/insecure
AgeCommit message (Collapse)Author
2018-01-048773 preseeded providers implementation for insecure flavorcyBerta
2017-12-12Add Splash StartActivityFup 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-09Merge 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-06reduce duplicate code in ConfigurationWizard for different flavorscyBerta
2017-11-06#8777 fixes NPEs and errorneous provider selectioncyBerta
2017-11-03#8778 fixes invalid provider error handlingcyBerta
2017-10-31#8757 new ProviderApiBase includes commonly used code between different ↵cyBerta
implementations of ProviderAPI
2017-10-29add missing import...cyBerta
2017-10-29#8757 refactores ProviderAPI for production flavorcyBerta
2017-10-28#8757 refactores ProviderAPI for insecure flavor, fixes tests, renames ↵cyBerta
confusing constants, updates robotium
2017-10-258757 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-21update ics-openvpn: update classes, manifest, resources and build scriptcyBerta
2016-02-06Update build tools and compile sdk version.Parménides GV
Warn about the needed libraries for 64 bit systems.
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).