public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug go/52341] New: crypto/rand FAILs before Solaris 11
@ 2012-02-22 18:03 ro at gcc dot gnu.org
  2012-04-25  4:42 ` [Bug go/52341] " ian at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: ro at gcc dot gnu.org @ 2012-02-22 18:03 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-04-25  4:43 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-22 18:03 [Bug go/52341] New: crypto/rand FAILs before Solaris 11 ro at gcc dot gnu.org
2012-04-25  4:42 ` [Bug go/52341] " ian at gcc dot gnu.org
2012-04-25  4:43 ` ian at airs dot com
2012-04-25  4:43 ` ian at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).