This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/52341] New: crypto/rand FAILs before Solaris 11
- From: "ro at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 22 Feb 2012 17:49:10 +0000
- Subject: [Bug go/52341] New: crypto/rand FAILs before Solaris 11
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52341
Bug #: 52341
Summary: crypto/rand FAILs before Solaris 11
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
AssignedTo: ian@airs.com
ReportedBy: ro@gcc.gnu.org
Host: *-*-solaris2.{8,9,10}
Target: *-*-solaris2.{8,9,10}
Build: *-*-solaris2.{8,9,10}
Before Solaris 11, the libgo crypto/rand test FAILs like this:
--- FAIL: rand.TestRead (0.00 seconds)
???:1: Read(buf) = 1040, %!s(<nil>)
FAIL
FAIL: crypto/rand
There's a limit on /dev/urandom here, while not properly documented in
random(7D), it can be found in the OpenSolaris sources and is alluded to in
Solaris 11 random(7D):
The limitation per read for /dev/random is 1040 bytes. The
limit for /dev/urandom is (128 * 1040).
The 1040 byte limit also applies to /dev/urandom before Solaris 11.
Rainer