github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-09 16:21:19 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #340] Upgrade tls client version to 1.2/1.3 #19874

New Issue
Closed
opened 2026-04-16 19:34:27 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-16 19:34:27 -05:00
Owner
Copy Link

Originally created by @mqus on GitHub (Jul 12, 2018).
Original GitHub issue: https://github.com/bitwarden/android/issues/340

Today I installed the self-hosted binary of bitwarden_rs and all clients worked fine.
Only the mobile app threw a "There is a problem connecting to the server" pretty much immediately when I tried to login.

After a while I found out that my reverse-proxy blocked the request:

Jul 12 22:53:54 myserver caddy[15936]: 2018/07/12 22:53:54 http: TLS handshake error from 12.34.56.78:42305: tls: client offered an unsupported, maximum protocol version of 301
Jul 12 22:53:54 myserver caddy[15936]: 2018/07/12 22:53:54 http: TLS handshake error from 12.34.56.78:42306: tls: client offered an unsupported, maximum protocol version of 300

It seems that the mobile app is still using TLS 1.0 (and even tried to use SSL 3.0). I can work around my specific error by configuring caddy (the reverse proxy) but TLS1.0 seems a bit insecure, even for sending already encrypted stuff.

Would it be possible to use/support TLS 1.2 or even 1.3?

Originally created by @mqus on GitHub (Jul 12, 2018). Original GitHub issue: https://github.com/bitwarden/android/issues/340 Today I installed the self-hosted binary of bitwarden_rs and all clients worked fine. Only the mobile app threw a "There is a problem connecting to the server" pretty much immediately when I tried to login. After a while I found out that my reverse-proxy blocked the request: ``` Jul 12 22:53:54 myserver caddy[15936]: 2018/07/12 22:53:54 http: TLS handshake error from 12.34.56.78:42305: tls: client offered an unsupported, maximum protocol version of 301 Jul 12 22:53:54 myserver caddy[15936]: 2018/07/12 22:53:54 http: TLS handshake error from 12.34.56.78:42306: tls: client offered an unsupported, maximum protocol version of 300 ``` It seems that the mobile app is still using TLS 1.0 (and even tried to use SSL 3.0). I can work around my specific error by configuring caddy (the reverse proxy) but TLS1.0 seems a bit insecure, even for sending already encrypted stuff. Would it be possible to use/support TLS 1.2 or even 1.3?
GiteaMirror commented 2026-04-16 19:34:28 -05:00
Author
Owner
Copy Link

@salquier commented on GitHub (Jul 14, 2018):

Hi,

I've also had some problem with my SSL configuration on my reverse-proxy.
I've solve my problems by using the nginx configuration generated by https://mozilla.github.io/server-side-tls/ssl-config-generator/.

Btw, the app work with TLS 1.2 (at least for android app).

<!-- gh-comment-id:405016261 --> @salquier commented on GitHub (Jul 14, 2018): Hi, I've also had some problem with my SSL configuration on my reverse-proxy. I've solve my problems by using the nginx configuration generated by https://mozilla.github.io/server-side-tls/ssl-config-generator/. Btw, the app work with TLS 1.2 (at least for android app).
GiteaMirror commented 2026-04-16 19:34:28 -05:00
Author
Owner
Copy Link

@mqus commented on GitHub (Jul 14, 2018):

Maybe it has to do with the Android version , I use Android 4.4.

<!-- gh-comment-id:405017163 --> @mqus commented on GitHub (Jul 14, 2018): Maybe it has to do with the Android version , I use Android 4.4.
GiteaMirror commented 2026-04-16 19:34:29 -05:00
Author
Owner
Copy Link

@mqus commented on GitHub (Jul 14, 2018):

I just researched a bit, this is indeed the case:
https://github.com/ssllabs/ssllabs-scan/issues/258

With solutions mentioned here.

<!-- gh-comment-id:405017335 --> @mqus commented on GitHub (Jul 14, 2018): I just researched a bit, this is indeed the case: https://github.com/ssllabs/ssllabs-scan/issues/258 With solutions mentioned [here.](https://github.com/auth0/Auth0.Android/issues/126)
GiteaMirror commented 2026-04-16 19:34:29 -05:00
Author
Owner
Copy Link

@salquier commented on GitHub (Jul 14, 2018):

Available but not enabled by default...
Solution for xamarin here.

<!-- gh-comment-id:405018530 --> @salquier commented on GitHub (Jul 14, 2018): Available but not enabled by default... Solution for xamarin [here](https://stackoverflow.com/questions/33112340/how-do-i-enable-tlsv1-1-on-xamarin-android-api-16-19).
GiteaMirror commented 2026-04-16 19:34:30 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jul 16, 2018):

Can you try latest build here? https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts

I added the mentioned fix using Play Services "Safety Net" for <= KitKat devices.

<!-- gh-comment-id:405238690 --> @kspearrin commented on GitHub (Jul 16, 2018): Can you try latest build here? https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts I added the mentioned fix using Play Services "Safety Net" for <= KitKat devices.
GiteaMirror commented 2026-04-16 19:34:30 -05:00
Author
Owner
Copy Link

@mqus commented on GitHub (Jul 16, 2018):

works perfectly!
thanks!

<!-- gh-comment-id:405243963 --> @mqus commented on GitHub (Jul 16, 2018): works perfectly! thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#19874
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?