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

update to use TLSv1.2 #295

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

update to use TLSv1.2 #295

wants to merge 1 commit into from

Conversation

seanlaval
Copy link

cloudant will not allow TLS 1 connections any more

cloudant will not allow TLS 1 connections any more
@chrisinmtown
Copy link

chrisinmtown commented Aug 5, 2019

Forgive me for asking a non-TLS question on this PR, but is the Ektorp project still active? Last commit seems to be Nov 2017; most recent PR before this was opened late 2018.

@YannRobert
Copy link
Collaborator

Hi @seanlaval could you please explain why you think this is necessary?

TLS 1.2 is enabled by default in Oracle JDK 8 since b122 (March 2014)
So you should have TLS 1.2 enabled already.

@YannRobert
Copy link
Collaborator

@chrisinmtown The project is not in active development, meaning no big change is expected to be merged, but PR on existing features may be merged when necessary. It turns out that most PR are not strictly necessary. Also you can extend or replace most of the component by your own for specific needs.

@seanlaval
Copy link
Author

@YannRobert it seems that the problem we saw might be due to using IBM java which has different default behaviour to Oracle java wrt Default SSL Context .. see https://www.ibm.com/support/knowledgecenter/en/SSYKE2_8.0.0/com.ibm.java.security.component.80.doc/security-component/jsse2Docs/matchsslcontext_tls.html

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

Successfully merging this pull request may close these issues.

3 participants