Skip to content
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

Inconsistencies with Android 8.1 client simulation #1333

Open
dilyanpalauzov opened this issue Sep 29, 2019 · 5 comments

Comments

@dilyanpalauzov
Copy link

commented Sep 29, 2019

./testssl.sh autoconfig.aegee.org prints:

 Running client simulations (HTTP) via sockets 
 Android 8.1 (native)         TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 253 bit ECDH (X25519)

but https://www.ssllabs.com/ssltest/analyze.html?d=autoconfig.aegee.org reports:

Handshake Simulation

Android 8.1 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384   ECDH x25519  FS
-- | -- | -- | --
@drwetter

This comment has been minimized.

Copy link
Owner

commented Sep 29, 2019

@dilyanpalauzov

This comment has been minimized.

Copy link
Author

commented Sep 29, 2019

I asked also at ssllabs/ssllabs-scan#749

@drwetter

This comment has been minimized.

Copy link
Owner

commented Sep 29, 2019

TLS 1.3. might have been added with an update though. It wasn't there in ~February(?) when I took this sample and the device was still alive.

If somebody has a recently patched device or a stronger Google-Fu, let me know.

@dilyanpalauzov

This comment has been minimized.

Copy link
Author

commented Sep 29, 2019

According to https://developer.android.com/about/versions/10/features#tls-1.3 TLS 1.3 was added to Android 10.

@drwetter

This comment has been minimized.

Copy link
Owner

commented Sep 30, 2019

I was about the post that too. But actually a stock Android 9 here had TLS 1.3 when it upgraded was from 8.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.