Conversation
doc/release-notes/release-4.sgml
Outdated
|
|
||
| <p>Also, be aware that the feature implementation is far from complete. The | ||
| popular SSL-Bump and certificate generation features are not yet supported | ||
| GnuTLS builds. Nor are many other less commonly used features. |
There was a problem hiding this comment.
s/GnuTLS builds/by GnuTLS builds/
doc/release-notes/release-4.sgml
Outdated
| upstream TLS connections. Then you now have the choice to build Squid with | ||
| GnuTLS instead of OpenSSL. | ||
| <p>Squid can now be built to use GnuTLS in place of OpenSSL for the core | ||
| features of receiving TLS connections from clients, and making TLS |
doc/release-notes/release-4.sgml
Outdated
| GnuTLS instead of OpenSSL. | ||
| <p>Squid can now be built to use GnuTLS in place of OpenSSL for the core | ||
| features of receiving TLS connections from clients, and making TLS | ||
| connection to servers. The GnuTLS support is still very much experimental |
There was a problem hiding this comment.
s/connection/connections/ for consistency with the previous "receiving" phrasing
| - TLS: GnuTLS implementation for listening ports and client connections | ||
| - TPROXY: Fix clientside_mark and client port logging | ||
| - Native FTP: Fix "Cannot assign requested address" with TPROXY | ||
| - SSL-Bump: Fix authentication with types other than Basic |
There was a problem hiding this comment.
FYI: The far more prevalent, historically accurate, and slightly more logical spelling is SslBump. This commit does not introduce this (minor) problem to ChangeLog, but it can fix it.
There was a problem hiding this comment.
Historically it has been a mix. "SSL-Bump" is to refer to the 'project' grouping I have for these patches generic patches. References to "SslBump" are mostly referring to the original 3.0/3.1 code functionality which went in by that name (or the way people titled their commits). I have been referring to the overall feature set as "SSL-Bump" since the mimic and generation features were added onto the "SslBump" feature.
FYI: The reason behind using that different name has been to stop new people wanting help going to the "SslBump" wiki page as their first stop for Squid-3.4+ configuration info. Big red deprecation warnings on the page did not help, but this subtle change to the terminology name being searched for in Google et al seems to have worked.
There was a problem hiding this comment.
"SSL-Bump" is to refer ...
SSL-Bump should not be used (for the reasons I have already provided). One cannot justify using a bad or inferior term by describing how it is to be used, by ignoring conflicting usages, or by mentioning bad wiki organization ideas, etc., etc. No need to respond though -- I have no time to fight this nonsense.
doc/release-notes/release-4.sgml
Outdated
| connection to servers. The GnuTLS support is still very much experimental | ||
| and should be tested before use. | ||
|
|
||
| <p>Also, be aware that the feature implementation is far from complete. The |
There was a problem hiding this comment.
You can drop the Also, be aware that fluff.
It is not clear what the feature is referring to. The earlier text talked about accepting and establishing TLS connections. It is not clear whether that implementation is incomplete, whether the SslBump features mentioned after this sentence are the missing parts, or whether some other important pieces are missing. What you have probably meant can be expressed like this:
GnuTLS coverage (of Squid features) is far from complete: SslBump and many other TLS-related features are not yet supported by GnuTLS builds.
You can keep or drop the parenthesized portion, depending on how precise you want this statement to be.
Any chance you can start using a far more common way to refer to versions? Like Also, this PR is not about v4 release notes but v4.0.24 release notes. It is best to be precise when it does not cost much. |
|
I think I mentioned it before, the "V4" is entirely generated by github. It uses the branch name when multiple commits are in the PR. |
* Add Americanism's to the release notes text. * Bump the release date to match rebiew delays.
|
GitHub is not responsible for Squid commit messages. I am sure you can fix it if you want to, regardless of what GitHub does by default. |
Also update mkrelease.sh script for git
2 participants
No description provided.