etesync-android

Commit Graph

Author	SHA1	Message	Date
Tom Hacohen	7d7096cc58	Allow connecting to insecure (http) servers. I'm a bit conflicted about this one because even though EteSync is end-to-end encrypted, people should be using TLS. I can't think of a reason why anyone would want to use HTTP over HTTPS, especially given let's encrypt exists and EteSync supports self-signed certs, but I guess it's better to allow it for now, at least until we have a nice error message for it. Fixes #81	5 years ago
Ricki Hirner	19ab4a14ce	Use cert4android instead of MemorizingTrustManager * use cert4android instead of MemorizingTrustManager * new app setting: distrust system certificates * add network security config to manifest so that user-installed CAs will be accepted in Android 7 again * update gradle	8 years ago

Author

SHA1

Message

Date

Tom Hacohen

7d7096cc58

Allow connecting to insecure (http) servers.

I'm a bit conflicted about this one because even though EteSync is
end-to-end encrypted, people should be using TLS.
I can't think of a reason why anyone would want to use HTTP over HTTPS,
especially given let's encrypt exists and EteSync supports self-signed
certs, but I guess it's better to allow it for now, at least until we
have a nice error message for it.

Fixes #81

Ricki Hirner

19ab4a14ce

Use cert4android instead of MemorizingTrustManager

* use cert4android instead of MemorizingTrustManager
* new app setting: distrust system certificates
* add network security config to manifest so that user-installed CAs will be accepted in Android 7 again
* update gradle

2 Commits (05182698123b29475135d8287c0b94bcfeb09133)