Skip to content

Conversation

@koushikthirupattur
Copy link
Contributor

@koushikthirupattur koushikthirupattur commented Feb 11, 2025

java.security.debug is a widely used debug system property for JDK security libs. It's time to capture details about this property via javadoc.

image

NOTE : We are adding a new html file (similar to the Networking Properties here) for documenting security-related properties, and over time, we will add more properties to this page.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change requires CSR request JDK-8350128 to be approved

Issues

  • JDK-8328914: Document the java.security.debug property in javadoc (Enhancement - P4)
  • JDK-8350128: Document the java.security.debug property in javadoc (CSR)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23569/head:pull/23569
$ git checkout pull/23569

Update a local copy of the PR:
$ git checkout pull/23569
$ git pull https://git.openjdk.org/jdk.git pull/23569/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 23569

View PR using the GUI difftool:
$ git pr show -t 23569

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23569.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Feb 11, 2025

👋 Welcome back koushikthirupattur! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Feb 11, 2025

@koushikthirupattur This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8328914: Document the java.security.debug property in javadoc

Reviewed-by: mullan

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 345 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@Michael-Mc-Mahon, @seanjmullan) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk
Copy link

openjdk bot commented Feb 11, 2025

@koushikthirupattur The following label will be automatically applied to this pull request:

  • security

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the security security-dev@openjdk.org label Feb 11, 2025
@koushikthirupattur koushikthirupattur marked this pull request as ready for review February 13, 2025 22:36
@openjdk openjdk bot added the rfr Pull request is ready for review label Feb 13, 2025
@mlbridge
Copy link

mlbridge bot commented Feb 13, 2025

@seanjmullan
Copy link
Member

@koushikthirupattur I think this will require a CSR. Even though it is a property that we have supported for a long time, I am pretty sure it is the first time we have documented it in the javadocs. Contact me if you need help writing the CSR.

@seanjmullan
Copy link
Member

/csr

@openjdk openjdk bot added the csr Pull request needs approved CSR before integration label Feb 14, 2025
@openjdk
Copy link

openjdk bot commented Feb 14, 2025

@seanjmullan has indicated that a compatibility and specification (CSR) request is needed for this pull request.

@koushikthirupattur please create a CSR request for issue JDK-8328914 with the correct fix version. This pull request cannot be integrated until the CSR request is approved.

@wangweij
Copy link
Contributor

Like what java/net did, we need a link from java/security/package-info.java to this new file.

@wangweij
Copy link
Contributor

Please also mention the +thread and +timestamp modifiers. Also, at the beginning, there is no default value for this system property. It is not false.

@wangweij
Copy link
Contributor

The ava sub-option for x509 is not included. BTW, I see the rows are in alphabetical order now, this is great. Can we also reorder the help output at

?

@koushikthirupattur
Copy link
Contributor Author

Like what java/net did, we need a link from java/security/package-info.java to this new file.

Added.

@koushikthirupattur
Copy link
Contributor Author

Please also mention the +thread and +timestamp modifiers. Also, at the beginning, there is no default value for this system property. It is not false.

Added.

@wangweij
Copy link
Contributor

The name and title should not be "Security Properties". This is about the debug system property.

@wangweij
Copy link
Contributor

Also, now we have the same content in 3 places:

  1. Here
  2. In the Security Guide at https://docs.oracle.com/en/java/javase/23/security/troubleshooting-security.html#GUID-05F3E865-20FF-46EB-AC35-84D4B552CA48
  3. At .
    Do we need to keep all of them? @seanjmullan

@seanjmullan
Copy link
Member

Also, now we have the same content in 3 places:

1. Here

2. In the Security Guide at https://docs.oracle.com/en/java/javase/23/security/troubleshooting-security.html#GUID-05F3E865-20FF-46EB-AC35-84D4B552CA48

3. At https://github.com/openjdk/jdk/blob/940aa7c4cf1bf770690660c8bb21fb3ddc5186e4/src/java.base/share/classes/sun/security/util/Debug.java#L85
   .
   Do we need to keep all of them? @seanjmullan

Well, I still find #3 valuable as it is useful as a command-line help option.

For #2, we don't need the duplication, but I think it is useful to still have a pointer from the guides to this new html file, so @koushikthirupattur please file a subtask (in the docs/guides category) to have the section in the security guide link to this new properties file in the javadoc.

@seanjmullan
Copy link
Member

The name and title should not be "Security Properties". This is about the debug system property.

Yes, this is because "Security Properties" are different than system properties, and are listed in the java.security file. We may want to someday also add them to this file, but not now. So, I would change it to "Security System Properties" or maybe "Security-Related System Properties"

@koushikthirupattur
Copy link
Contributor Author

Also, now we have the same content in 3 places:

1. Here

2. In the Security Guide at https://docs.oracle.com/en/java/javase/23/security/troubleshooting-security.html#GUID-05F3E865-20FF-46EB-AC35-84D4B552CA48

3. At https://github.com/openjdk/jdk/blob/940aa7c4cf1bf770690660c8bb21fb3ddc5186e4/src/java.base/share/classes/sun/security/util/Debug.java#L85
   .
   Do we need to keep all of them? @seanjmullan

Well, I still find #3 valuable as it is useful as a command-line help option.

For #2, we don't need the duplication, but I think it is useful to still have a pointer from the guides to this new html file, so @koushikthirupattur please file a subtask (in the docs/guides category) to have the section in the security guide link to this new properties file in the javadoc.

Created here 8350384

@koushikthirupattur
Copy link
Contributor Author

The name and title should not be "Security Properties". This is about the debug system property.

Yes, this is because "Security Properties" are different than system properties, and are listed in the java.security file. We may want to someday also add them to this file, but not now. So, I would change it to "Security System Properties" or maybe "Security-Related System Properties"

Changed.

@wangweij
Copy link
Contributor

The +thread and +timestamp are modifiers that can be added to any value. I'd like them to be described outside the table.

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 4, 2025

@koushikthirupattur 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!

@openjdk
Copy link

openjdk bot commented Apr 29, 2025

⚠️ @koushikthirupattur the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout 8328914
$ git commit --author='Preferred Full Name <you@example.com>' --allow-empty -m 'Update full name'
$ git push

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed csr Pull request needs approved CSR before integration labels Apr 29, 2025
@koushikthirupattur
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label May 1, 2025
@openjdk
Copy link

openjdk bot commented May 1, 2025

@koushikthirupattur
Your change (at version f53973f) is now ready to be sponsored by a Committer.

@seanjmullan
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented May 1, 2025

Going to push as commit 394961c.
Since your change was applied there have been 346 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 1, 2025
@openjdk openjdk bot closed this May 1, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels May 1, 2025
@openjdk
Copy link

openjdk bot commented May 1, 2025

@seanjmullan @koushikthirupattur Pushed as commit 394961c.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integrated Pull request has been integrated security security-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

5 participants