-
Notifications
You must be signed in to change notification settings - Fork 16
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
Added the OpenSSL version requirement #216
Merged
AlexicaWright
merged 3 commits into
neo4j:dev
from
alexnb:add-openssl-version-requirement
Apr 26, 2024
Merged
Added the OpenSSL version requirement #216
AlexicaWright
merged 3 commits into
neo4j:dev
from
alexnb:add-openssl-version-requirement
Apr 26, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
ravikiran-sulikeri
approved these changes
Apr 19, 2024
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.
LGTM 👍
AlexicaWright
pushed a commit
to AlexicaWright/docs-ops-manager
that referenced
this pull request
Apr 26, 2024
* added the OpenSSL version requirement * minor * minor corrections
AlexicaWright
pushed a commit
to AlexicaWright/docs-ops-manager
that referenced
this pull request
Apr 26, 2024
* added the OpenSSL version requirement * minor * minor corrections
AlexicaWright
pushed a commit
to AlexicaWright/docs-ops-manager
that referenced
this pull request
Apr 26, 2024
* added the OpenSSL version requirement * minor * minor corrections
AlexicaWright
added a commit
that referenced
this pull request
Apr 26, 2024
AlexicaWright
added a commit
that referenced
this pull request
Apr 26, 2024
AlexicaWright
added a commit
that referenced
this pull request
Apr 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since one of the customers had a problem with SSL certificates generated by an older version of OpenSSL, customer support asked to add a more explicit requirement (we just had some info on the self-signed SSL generation page).
OpenSSL 3.0.x is LTS and will be supported until September 2026, so I think it is fine to recommend it.
If you open a PR that needs to go into a current version, you need to cherry-pick your commit from dev over to the current version branch. Only then will the proper builds that generate html/pdf be run. But beware: Docs will be generated but not published automatically!