We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDKs before 27 allow clear text (non-https) by default. This is a security vulnerability since the minimum SDK is 21.
Basically, it allows man-in-the-middle attacks.
Steps to reproduce:
Expected behavior All network traffic restricted to HTTPS
Screenshots
This is discussed more here: https://developer.android.com/privacy-and-security/risks/cleartext
Environment (please complete the following information):
Additional context If no HTTPS becomes an issue for testing, we must add flavour configurations instead.
The text was updated successfully, but these errors were encountered:
Merge pull request #546 from OpenArchive/feature/541-restrict-clear-t…
d13c0c9
…ext-traffic fix(network config): restrict clear text by default #541
Hi @vanichitkara this would be extremely hard to test explicitly, but is available in an internal test build (version 0.3.2)
I would recommend exercising any features that use the web (storage, uploads)
If you have a proxy such as Charles or mitmproxy to log http traffic that would be a bonus.
Feel free to close if you do not experience any issues related to networks.
Sorry, something went wrong.
vanichitkara
No branches or pull requests
SDKs before 27 allow clear text (non-https) by default. This is a security vulnerability since the minimum SDK is 21.
Basically, it allows man-in-the-middle attacks.
Steps to reproduce:
Expected behavior
All network traffic restricted to HTTPS
Screenshots
This is discussed more here: https://developer.android.com/privacy-and-security/risks/cleartext
Environment (please complete the following information):
Additional context
If no HTTPS becomes an issue for testing, we must add flavour configurations instead.
The text was updated successfully, but these errors were encountered: