OPENJDK-4113: stop adjusting securerandom.source #613
Conversation
Since kernel v5.6 (2020), /dev/random no longer blocks and is functionally equivalent to /dev/urandom. So there's no point in adjusting securerandom.source. Signed-off-by: Jonathan Dowland <[email protected]>
|
Should we consider this for ubi9 too? |
There was a problem hiding this comment.
OK. This should be in some form of release note and mentioning the -Djava.security.egd=file:/dev/urandom workaround. Note that while newer kernels treat them, /dev/random and /dev/urandom, equivalently, we don't know on which host system the image will run. It might be RHEL-9, or ... The container compatibility matrix from OCP might come in handy here.
No. Similar to other "larger" changes. Let's leave ubi9 alone as much as possible. |
|
Aside: Can we disable the label/JIRA issue action until it's fixed? |
Sure. I've no idea why it's broken. It worked for about a day, and then stopped. |
Since kernel v5.6 (2020), /dev/random no longer blocks and is functionally equivalent to /dev/urandom. So there's no point in adjusting securerandom.source.
OPENJDK-4113