bitmask_android.git/app/src/insecure/java, branch develop [bitmask_android] update ics-openvpn: update classes, manifest, resources and build script 2017-09-20T23:28:24+00:00 cyBerta cyberta@riseup.net 2017-09-20T23:28:24+00:00 d77b9aefea75491b50f28a6880906ba9496979f2 






Update build tools and compile sdk version.
2016-02-06T11:42:42+00:00

Parménides GV
parmegv@sdf.org

2016-02-06T11:42:42+00:00

096faf08f2d0cc4dc4a28677415391942410063d

Warn about the needed libraries for 64 bit systems.





Warn about the needed libraries for 64 bit systems.







s/buildtype/flavor, changed riseup's pin
2015-06-08T18:04:03+00:00

Parménides GV
parmegv@sdf.org

2015-06-08T17:56:43+00:00

b0a0805ab81aaa4e204ecfc77d3a6a7f7ed66b2f

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).





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).