-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
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
OOM on Android 8/9 when getting "https://icloud.com" #4155
Comments
Interesting bug. Please also report to the conscrypt tracker. |
I have created an issue for conscrypt too. The questionable certificate seems to be:
Interestingly, I don't see an alias for |
As I noted in google/conscrypt#520, it looks like icloud.com returns that cert (which is for images.apple.com) when SNI isn't provided in the handshake, which makes some sense, but that implies that either OkHttp isn't enabling SNI properly or Conscrypt isn't handling it properly. So independent of the OOM, it looks like there's another problem with SNI lurking somewhere. |
I have to apologize. Maybe I got the cert from openssl when debugging and took the wrong one. You would have to see what cert okhttp uses directly. |
Same test, similar (but not the same) exception again today:
|
Yikes. |
Working with later releases and a conscrypt issue anyway |
Hello,
When trying to
GET
(orPROPFIND
) https://icloud.com (without www) with code like that:it takes a long time until the process is killed with OOM and the test fails:
This happens with Android 8.0 and 9.0 (emulator from SDK), but not with Android 4.4 (haven't tested other versions yet).
The problem occurs with okhttp 3.10.0 and 3.11.0 (haven't tested other versions yet).
Everything is working for some other URLs I have tested, including www.icloud.com. It seems to be related to parsing the certificate. When using a custom trust manager (from https://gitlab.com/bitfireAT/cert4android), it works.
I don't know whether this is an okhttp problem (looks like an Android problem?), but I guess it's quite important to understand why a simple
GET
request causes the whole process to crash.The text was updated successfully, but these errors were encountered: