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

chore: set the minimum TLS version in the client to v1.2 #156

Merged
merged 3 commits into from
Mar 16, 2022
Merged

Conversation

pyrooka
Copy link
Member

@pyrooka pyrooka commented Mar 8, 2022

This PR changes the client in the base service to require
at least TLS v1.2 for secure communication with the server.

@pyrooka pyrooka requested a review from padamstx March 8, 2022 19:43
Copy link
Member

@padamstx padamstx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!
Just need to perhaps add an extra test for a retryable client.

Edit: oh and one more thing... this commit should probably have a "feat" type prefix so we get a new minor version.

Edit 2: I think we need to also test these changes with a couple of integration tests within the platform-services go SDK just to make sure that these changes work correctly with some actual IBM Cloud services.

v5/core/base_service_test.go Show resolved Hide resolved
v5/core/base_service_test.go Show resolved Hide resolved
@pyrooka pyrooka merged commit 0188990 into main Mar 16, 2022
@pyrooka pyrooka deleted the http-min-tls branch March 16, 2022 19:03
ibm-devx-sdk pushed a commit that referenced this pull request Mar 16, 2022
## [5.9.3](v5.9.2...v5.9.3) (2022-03-16)

### Bug Fixes

* set the minimum TLS version in the client to v1.2 ([#156](#156)) ([0188990](0188990))
@ibm-devx-sdk
Copy link

🎉 This PR is included in version 5.9.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants