Fix outdated ssl:// transport description and clarify TLS behavior #5088
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.
Summary
The documentation for the
ssl://stream transport currently states that itnegotiates SSLv2 or SSLv3 connections. This is outdated and misleading.
Since PHP 5.6 (Improved TLS Defaults RFC), SSLv2 and SSLv3 are obsolete,
insecure, and no longer enabled by default in modern PHP/OpenSSL builds.
In practice,
ssl://negotiates the best available SSL/TLS protocol basedon client and server capabilities, OpenSSL configuration, and optional
stream context settings (e.g.
ssl.crypto_method).Changes
ssl://to reflect modern SSL/TLS negotiation.sslv2://andsslv3://examples while keeping thetransports documented for backward compatibility.
Rationale
This aligns the documentation with actual PHP behavior and with the
"Improved TLS Defaults" RFC, while preserving backward compatibility and
avoiding API changes.
References
https://wiki.php.net/rfc/improved-tls-defaults