Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

The value set for securerandom.source in  $JAVA_HOME/jre/lib/security/java.security is /dev/urandom but for some reason java sees this as /dev/random and jvm startup times are slow when they rely on this. Instead it should be /dev/./urandom

Version-Release number of selected component (if applicable):


How reproducible:

Run an app with the default settings that relies on this file.

Steps to Reproduce:
1. Install Sun Java RPM or OpenJDK RPM
2. Run app utilizing securerandom.source 
3.

Actual results:

Startup times are very slow while /dev/random sorts out randomness.

Expected results:

/dev/urandom is used and startup times are fast.

Additional info:

See

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6202721

As a workaround

-Djava.security.egd=file:/dev/./urandom

can be set, but it seems the intention of using /de/urandom is to avoid this problem and therefor should be /dev/./urandom

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

The provided bug link in the original comment no longer works. However this has been brought up before. urandom does not provide as strong an initial seed as urandom and is therefore intentionally not the default:

https://bugs.openjdk.java.net/browse/JDK-4705093

Closing as WONTFIX.