ssl session cache, exportable flag #16322
Closed
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
Give peers and `exportable` flag, set TRUE when sessions for this peer should not be exported. This evalualtes if the peer uses confidential information (like srp username/password), a client certificate OR if the "ssl_peer_key" contains relative paths. When SSL is configured with paths for relevant components, like CA trust anchors, an attempt is made to make this path absolute. When that does not work or the infrstructure is not available, the peer key is marked as *local*. Exporting sessions based on relative paths may lead to confusion when later imported in another execution context.
Really? Was this a typo? It sounds... odd. |
Typo for proof of humanity. |
bagder
approved these changes
Feb 17, 2025
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.
Add flag
exportableto SSL session cache peers, set to TRUE when sessions for this peer can be exported. This evalualtes if the peer uses confidential information (like srp username/password), a client certificate OR if the "ssl_peer_key" contains relative paths.When SSL is configured with paths for relevant components, like CA trust anchors, an attempt is made to make this path absolute. When that does not work or the infrstructure is not available, the peer key is marked as local.
Exporting sessions based on relative paths may lead to confusion when later imported in another execution context.