IcoreE opened a new pull request, #1503: URL: https://github.com/apache/commons-lang/pull/1503
[LANG-1794] (https://issues.apache.org/jira/browse/LANG-1794) The current JavaDoc for RandomUtils.secure() states that it “uses an algorithms/providers specified in the securerandom.strongAlgorithms Security property.” This is misleading. In reality: 1. RandomUtils.secure() uses new SecureRandom() and does not consult the securerandom.strongAlgorithms property. 2. The securerandom.strongAlgorithms property is only used by RandomUtils.secureStrong(), which internally calls SecureRandom.getInstanceStrong() to select a strong algorithm from the configured security providers <img width="1145" height="424" alt="image" src="https://github.com/user-attachments/assets/2fde4826-6b8d-41a0-adbd-4810d4e99808"; /> Thanks for your contribution to [Apache Commons](https://commons.apache.org/)! Your help is appreciated! Before you push a pull request, review this list: - [ ] Read the [contribution guidelines](CONTRIBUTING.md) for this project. - [ ] Read the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) if you use Artificial Intelligence (AI). - [ ] I used AI to create any part of, or all of, this pull request. - [ ] Run a successful build using the default [Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command line by itself. - [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Each commit in the pull request should have a meaningful subject line and body. Note that a maintainer may squash commits during the merge process. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
