Bug 1016361

Summary:	securerandom.source value in $JAVA_HOME/jre/lib/security/java.security is incorrect
Product:	Red Hat Enterprise Linux 6	Reporter:	August Simonelli <asimonel>
Component:	java-1.6.0-sun	Assignee:	jiri vanek <jvanek>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.4	CC:	dbhole, jvanek, pablo.iranzo
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-06 22:00:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description August Simonelli 2013-10-08 03:07:12 UTC

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

Comment 1 August Simonelli 2013-10-08 03:08:19 UTC

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

Comment 3 RHEL Program Management 2013-10-13 23:03:09 UTC

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.

Comment 5 Deepak Bhole 2014-05-06 22:00:35 UTC

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.