Is this the best way to deprecate support for the srandom and urandom devices? The devices themselves are going to stick around for a while, but we only need to tell people about one, right?
Index: random.4 =================================================================== RCS file: /home/tedu/cvs/src/share/man/man4/random.4,v retrieving revision 1.22 diff -u -r1.22 random.4 --- random.4 10 Oct 2008 20:13:29 -0000 1.22 +++ random.4 2 Oct 2010 15:57:32 -0000 @@ -28,8 +28,6 @@ .Os .Sh NAME .Nm random , -.Nm srandom , -.Nm urandom , .Nm arandom .Nd random data source devices .Sh SYNOPSIS @@ -43,22 +41,10 @@ Entropy data is collected from system activity (like disk and network device interrupts and such), and then run through various hash or message digest functions to generate the output. -.Bl -hang -width /dev/srandomX +.Bl -hang -width /dev/arandomX .It Pa /dev/random This device is reserved for future support of hardware random generators. -.It Pa /dev/srandom -Strong random data. -This device returns reliable random data. -If sufficient entropy is not currently available (i.e., the entropy -pool quality starts to run low), the driver pauses while more of -such data is collected. -The entropy pool data is converted into output data using MD5. -.It Pa /dev/urandom -Same as above, but does not guarantee the data to be strong. -The entropy pool data is converted into output data using MD5. -When the entropy pool quality runs low, the driver will continue -to output data. .It Pa /dev/arandom As required, entropy pool data re-seeds an ARC4 generator, which then generates high-quality pseudo-random output data. @@ -69,10 +55,8 @@ providing a second level of ARC4 hashed data. .El .Sh FILES -.Bl -tag -width /dev/srandom -compact +.Bl -tag -width /dev/arandom -compact .It Pa /dev/random -.It Pa /dev/srandom -.It Pa /dev/urandom .It Pa /dev/arandom .El .Sh SEE ALSO
