Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Jacques RascagneresJacques RascagneresReporter
Ben BrooksBen BrooksStory Points
1Components
Sprint
NoneFix versions
Priority
MajorInstabug
Open Instabug
Details
Details
Assignee
Jacques Rascagneres
Jacques RascagneresReporter
Ben Brooks
Ben BrooksStory Points
1
Components
Sprint
None
Fix versions
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created March 22, 2021 at 11:47 AM
Updated March 30, 2021 at 6:09 PM
Resolved March 25, 2021 at 4:39 PM
Was done in Server as https://couchbasecloud.atlassian.net/browse/MB-41794#icft=MB-41794, might be worth considering bumping ours too, which is currently still at TLS1.0 - we chose the TLS1.0 default instead of TLS1.2 to align with Server at the time.
This config setting controls the publicly facing HTTP APIs when served with TLS (not related to any kind of connection to Server).
Compatibility: with browsers/mobile platforms can be found here:
https://support.globalsign.com/ssl/general-ssl/tls-protocol-compatibility
Android 5+ (2014) - CBL 2.6 was the last release to have deprecated support for Android 4/API 19, so that's our last potential "partial" compatibility.
iOS 5+ (2011) - CBL 2.0+ requires iOS 9
Regardless of this compatibility, the min TLS version can still be lowered back down to TLS 1.0 via
tls_minimum_version=tlsv1
if customers have a requirement to use unsupported devices.Implementation: bump this const to tls.VersionTLS12!
config.go:46 const DefaultMinimumTLSVersionConst = tls.VersionTLS10