-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8044609: javax.net.debug options not working and documented as expected #18764
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
base: master
Are you sure you want to change the base?
Conversation
|
👋 Welcome back coffeys! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
Webrevs
|
|
Tidied up the help menu output to capture current options |
src/java.base/share/classes/sun/security/ssl/CertificateMessage.java
Outdated
Show resolved
Hide resolved
|
@coffeys This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
|
@coffeys This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
|
/open |
|
@coffeys This pull request is now open |
|
@coffeys This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
|
@coffeys this pull request can not be integrated into git checkout 8044609-ssl
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
@coffeys This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
|
/open |
|
@coffeys This pull request is now open |
|
@coffeys This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
|
Reminder on this one @bradfordwetmore |
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.
Initial comments for current SSLLogger.
Continuing next week.
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.
Thanks for initial comments Brad. I've taken them on board.
The sub-component parsing logic might have been needlessly complex. I've introduced a new isSubComponent field directly to the new Opt enum. That helps query components and simplify the code,
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.
Next set of comments. Thanks for addressing the previous set!
| if (SSLLogger.isOn && | ||
| SSLLogger.isOn("ssl,handshake,verbose")) { | ||
| if (SSLLogger.logging && | ||
| SSLLogger.isOn(SSLLogger.Opt.HANDSHAKE_VERBOSE)) { |
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.
Not your fault, but I'm not sure I like this as a verbose message.
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.
In agreement. This sort of message strikes me as more in the HANDSHAKE category
Will I log a follow on JBS issue to have all call sites of Opt examined ?
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.
Thanks again for the review comments Brad. I've made comments and corrections where raised. New changes pushed.
| if (SSLLogger.isOn && | ||
| SSLLogger.isOn("ssl,handshake,verbose")) { | ||
| if (SSLLogger.logging && | ||
| SSLLogger.isOn(SSLLogger.Opt.HANDSHAKE_VERBOSE)) { |
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.
In agreement. This sort of message strikes me as more in the HANDSHAKE category
Will I log a follow on JBS issue to have all call sites of Opt examined ?
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.
A couple more minor comments.
All copyrights look good. (Thanks.)
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.
Thanks for comments Brad. All should be addressed.
|
@coffeys This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
The
javax.net.debugTLS debug option is buggy since TLSv1.3 implementation was introduced many years ago.Where "ssl" was previously a value to obtain all TLS debug traces (except network type dumps, verbose data), it now prints only a few lines for a standard client TLS connection.
The property parsing was also lax and allowed users to declare verbose logging options by themselves where the documentation stated that such verbose options were only meant to be used in conjunction with other TLS options :
as part of this patch, I've also moved the log call to the more performant friendly
System.Logger#log(java.lang.System.Logger.Level,java.util.function.Supplier)method.the output has changed slightly with respect to that - less verbose
e.g. old style:
e.g. new format:
note one line less per verbose entry and dropping of brackets around verbose output
new test case added to exercise
javax.net.debugoptions including the use of theSystem.Loggeroption.Progress
Issues
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18764/head:pull/18764$ git checkout pull/18764Update a local copy of the PR:
$ git checkout pull/18764$ git pull https://git.openjdk.org/jdk.git pull/18764/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18764View PR using the GUI difftool:
$ git pr show -t 18764Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18764.diff
Using Webrev
Link to Webrev Comment