-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add a note about supporting TLS in the README.md #217
Conversation
``` | ||
|
||
Please ensure that your OpenSSL version supports TLS v1.1 or higher. You can view the change log for OpenSSL here: https://www.openssl.org/news/changelog.html. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That link doesn't work with the .
on the end. I pulled it up and I've got no idea how I'd determine which versions support it. Can you dig through there and come up with a list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@drewish does the markdown file include the period .
as part the URL? When I view the branch on github, it properly renders the link without the period. Did you simply copy/past the link with the period?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to account for both people looking at it on GitHub and people looking at it in their editor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@drewish period removed.
It might be good to add the minimum OpenSSL version too so people don't have to dig. I think it's 1.0.1 but I will need to check. |
@bhelx it's 1.0.1g - or at least that's the one where they fixed heartbleed. Should that be the minimum version? |
5753d84
to
42dd7fb
Compare
Ok - so initial TLSv1.1 support starts with v1.0.1. This was cataloged in "Changes between 1.0.0h and 1.0.1": https://www.openssl.org/news/changelog.html#x21 -- note: it's described in the last bullet point:
However, since 1.0.1 also introduced heartbleed, I think we should recommend versions 1.0.1g and up -- 1.0.1g was the version that fixed heartbleed: https://www.openssl.org/news/changelog.html#x14
As far as the "best" version, I think it's 1.1.0 since it "prefers" TLS v1.2: It's a number of bullet points down:
|
fd87ffb
to
c2367ad
Compare
Ok, based on the info above, I changed the wording to:
|
👍 |
@rafdizzle86 agreed, thoughtful consideration |
👍 |
I think it would be helpful for users of this library to know they should utilize an OpenSSL version to one that is using TLS v1.1+ since Recurly will slowly be deprecating any protocols that do not use TLS v1.1.