10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
In our HP-UX B.11.11. I could not find dev/urandom and dev/random
Are all pseudo-devices implemented as device drivers, or in need to run /configure some package to install the package to have dev/urandom.
Please help (4 Replies)
Discussion started by: rashi
4 Replies
2. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
Write a shell script that will take the sum of two random number?
Ex: Random n1 +Random n2 = result
i tries to write it but i had some dufficulties
... (3 Replies)
Discussion started by: renegade755
3 Replies
3. Shell Programming and Scripting
i want to generate a random number through a script, and even if anyone reads the script, they wont be able to figure out what the random number is. only the person who setup the script would know it.
something like this could work: random
the full thread is here:
... (13 Replies)
Discussion started by: SkySmart
13 Replies
4. Shell Programming and Scripting
I have a for loop that cycles twice and generates 1 random number for each pass through. I would like to be able to store the two numbers to use later for arithmetics. Is there a way to do that? Right now I can only seem to use the last random number for anything. Thanks. (4 Replies)
Discussion started by: AxlVanDamme
4 Replies
5. Shell Programming and Scripting
Hi Can someone help me with this one?
I have string..
(PROC_PROC_ID == 12183) <--PID is dynamic
and i want to replace the PID number with whatever PID from
/opt/hpws/apache32_2/logs/httpd.pid file.
i'm having problem since the PID on the string is dynamic. It may be 2-5 digits or more.
... (5 Replies)
Discussion started by: ryandegreat25
5 Replies
6. Shell Programming and Scripting
Hi,
I am having trouble with generating random numbers. can this be done with awk?
So I have a file that looks like this:
23 30
24 40
26 34
So column1 is start and column2 is end. I want to generate 3 random #'s between start and stop:
So the output will look like this:
... (9 Replies)
Discussion started by: phil_heath
9 Replies
7. Shell Programming and Scripting
Hi Guys I have a script to find Ranomd numbers. But I want to make the file to produce more random. Could u guys help me plz.
In this Script I have the code that generates random in for loop and the range I have specified in my %chromlength
input and out put will be like this
chrno start end... (3 Replies)
Discussion started by: repinementer
3 Replies
8. Shell Programming and Scripting
Hello All,
I want to make a simple script which generate random number from 0 to 1000.
and simply display it.
Plz HELP!!!!!!
Regards,
Waqas Ahmed (2 Replies)
Discussion started by: wakhan
2 Replies
9. Programming
Hi,
I am currently trying to generate multiple random numbers in C for different variable:-
die1=1+(rand()%5);
die2=1+(rand()%5);
die3=1+(rand()%5);
die4=1+(rand()%5);
But I need to contrain the total of die1, die2,die3 and die4 to be 5 as well. If i insert die1+die2+die3+die4=5, i do... (6 Replies)
Discussion started by: ahjiefreak
6 Replies
10. UNIX for Dummies Questions & Answers
Is anyone know some scripts to generate random number without repetition using bash; for example generate 10 different random numbers.
Thanks (8 Replies)
Discussion started by: asal_email
8 Replies
RANDOM(4) Linux Programmer's Manual RANDOM(4)
NAME
random, urandom - kernel random number source devices
DESCRIPTION
The character special files /dev/random and /dev/urandom (present since Linux 1.3.30) provide an interface to the kernel's random number
generator. File /dev/random has major device number 1 and minor device number 8. File /dev/urandom has major device number 1 and minor
device number 9.
The random number generator gathers environmental noise from device drivers and other sources into an entropy pool. The generator also
keeps an estimate of the number of bits of noise in the entropy pool. From this entropy pool random numbers are created.
When read, the /dev/random device will only return random bytes within the estimated number of bits of noise in the entropy pool.
/dev/random should be suitable for uses that need very high quality randomness such as one-time pad or key generation. When the entropy
pool is empty, reads from /dev/random will block until additional environmental noise is gathered.
A read from the /dev/urandom device will not block waiting for more entropy. As a result, if there is not sufficient entropy in the
entropy pool, the returned values are theoretically vulnerable to a cryptographic attack on the algorithms used by the driver. Knowledge
of how to do this is not available in the current unclassified literature, but it is theoretically possible that such an attack may exist.
If this is a concern in your application, use /dev/random instead.
Usage
If you are unsure about whether you should use /dev/random or /dev/urandom, then probably you want to use the latter. As a general rule,
/dev/urandom should be used for everything except long-lived GPG/SSL/SSH keys.
If a seed file is saved across reboots as recommended below (all major Linux distributions have done this since 2000 at least), the output
is cryptographically secure against attackers without local root access as soon as it is reloaded in the boot sequence, and perfectly ade-
quate for network encryption session keys. Since reads from /dev/random may block, users will usually want to open it in nonblocking mode
(or perform a read with timeout), and provide some sort of user notification if the desired entropy is not immediately available.
The kernel random-number generator is designed to produce a small amount of high-quality seed material to seed a cryptographic pseudo-ran-
dom number generator (CPRNG). It is designed for security, not speed, and is poorly suited to generating large amounts of random data.
Users should be very economical in the amount of seed material that they read from /dev/urandom (and /dev/random); unnecessarily reading
large quantities of data from this device will have a negative impact on other users of the device.
The amount of seed material required to generate a cryptographic key equals the effective key size of the key. For example, a 3072-bit RSA
or Diffie-Hellman private key has an effective key size of 128 bits (it requires about 2^128 operations to break) so a key generator only
needs 128 bits (16 bytes) of seed material from /dev/random.
While some safety margin above that minimum is reasonable, as a guard against flaws in the CPRNG algorithm, no cryptographic primitive
available today can hope to promise more than 256 bits of security, so if any program reads more than 256 bits (32 bytes) from the kernel
random pool per invocation, or per reasonable reseed interval (not less than one minute), that should be taken as a sign that its cryptog-
raphy is not skilfully implemented.
Configuration
If your system does not have /dev/random and /dev/urandom created already, they can be created with the following commands:
mknod -m 644 /dev/random c 1 8
mknod -m 644 /dev/urandom c 1 9
chown root:root /dev/random /dev/urandom
When a Linux system starts up without much operator interaction, the entropy pool may be in a fairly predictable state. This reduces the
actual amount of noise in the entropy pool below the estimate. In order to counteract this effect, it helps to carry entropy pool informa-
tion across shut-downs and start-ups. To do this, add the following lines to an appropriate script which is run during the Linux system
start-up sequence:
echo "Initializing random number generator..."
random_seed=/var/run/random-seed
# Carry a random seed from start-up to start-up
# Load and then save the whole entropy pool
if [ -f $random_seed ]; then
cat $random_seed >/dev/urandom
else
touch $random_seed
fi
chmod 600 $random_seed
poolfile=/proc/sys/kernel/random/poolsize
[ -r $poolfile ] && bytes=`cat $poolfile` || bytes=512
dd if=/dev/urandom of=$random_seed count=1 bs=$bytes
Also, add the following lines in an appropriate script which is run during the Linux system shutdown:
# Carry a random seed from shut-down to start-up
# Save the whole entropy pool
echo "Saving random seed..."
random_seed=/var/run/random-seed
touch $random_seed
chmod 600 $random_seed
poolfile=/proc/sys/kernel/random/poolsize
[ -r $poolfile ] && bytes=`cat $poolfile` || bytes=512
dd if=/dev/urandom of=$random_seed count=1 bs=$bytes
/proc Interface
The files in the directory /proc/sys/kernel/random (present since 2.3.16) provide an additional interface to the /dev/random device.
The read-only file entropy_avail gives the available entropy. Normally, this will be 4096 (bits), a full entropy pool.
The file poolsize gives the size of the entropy pool. The semantics of this file vary across kernel versions:
Linux 2.4: This file gives the size of the entropy pool in bytes. Normally, this file will have the value 512, but it is writable,
and can be changed to any value for which an algorithm is available. The choices are 32, 64, 128, 256, 512, 1024, or
2048.
Linux 2.6: This file is read-only, and gives the size of the entropy pool in bits. It contains the value 4096.
The file read_wakeup_threshold contains the number of bits of entropy required for waking up processes that sleep waiting for entropy from
/dev/random. The default is 64. The file write_wakeup_threshold contains the number of bits of entropy below which we wake up processes
that do a select(2) or poll(2) for write access to /dev/random. These values can be changed by writing to the files.
The read-only files uuid and boot_id contain random strings like 6fd5a44b-35f4-4ad4-a9b9-6b9be13e1fe9. The former is generated afresh for
each read, the latter was generated once.
FILES
/dev/random
/dev/urandom
SEE ALSO
mknod (1)
RFC 1750, "Randomness Recommendations for Security"
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2010-08-29 RANDOM(4)