⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 random.c

📁 powerpc内核mpc8241linux系统下char驱动程序
💻 C
📖 第 1 页 / 共 4 页
字号:
/* * random.c -- A strong random number generator * * Version 1.04, last modified 26-Apr-98 *  * Copyright Theodore Ts'o, 1994, 1995, 1996, 1997, 1998.  All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright *    notice, and the entire permission notice in its entirety, *    including the disclaimer of warranties. * 2. Redistributions in binary form must reproduce the above copyright *    notice, this list of conditions and the following disclaimer in the *    documentation and/or other materials provided with the distribution. * 3. The name of the author may not be used to endorse or promote *    products derived from this software without specific prior *    written permission. *  * ALTERNATIVELY, this product may be distributed under the terms of * the GNU Public License, in which case the provisions of the GPL are * required INSTEAD OF the above restrictions.  (This clause is * necessary due to a potential bad interaction between the GPL and * the restrictions contained in a BSD-style copyright.) *  * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED * OF THE POSSIBILITY OF SUCH DAMAGE. *//* * (now, with legal B.S. out of the way.....)  *  * This routine gathers environmental noise from device drivers, etc., * and returns good random numbers, suitable for cryptographic use. * Besides the obvious cryptographic uses, these numbers are also good * for seeding TCP sequence numbers, and other places where it is * desirable to have numbers which are not only random, but hard to * predict by an attacker. * * Theory of operation * =================== *  * Computers are very predictable devices.  Hence it is extremely hard * to produce truly random numbers on a computer --- as opposed to * pseudo-random numbers, which can easily generated by using a * algorithm.  Unfortunately, it is very easy for attackers to guess * the sequence of pseudo-random number generators, and for some * applications this is not acceptable.  So instead, we must try to * gather "environmental noise" from the computer's environment, which * must be hard for outside attackers to observe, and use that to * generate random numbers.  In a Unix environment, this is best done * from inside the kernel. *  * Sources of randomness from the environment include inter-keyboard * timings, inter-interrupt timings from some interrupts, and other * events which are both (a) non-deterministic and (b) hard for an * outside observer to measure.  Randomness from these sources are * added to an "entropy pool", which is mixed using a CRC-like function. * This is not cryptographically strong, but it is adequate assuming * the randomness is not chosen maliciously, and it is fast enough that * the overhead of doing it on every interrupt is very reasonable. * As random bytes are mixed into the entropy pool, the routines keep * an *estimate* of how many bits of randomness have been stored into * the random number generator's internal state. *  * When random bytes are desired, they are obtained by taking the SHA * hash of the contents of the "entropy pool".  The SHA hash avoids * exposing the internal state of the entropy pool.  It is believed to * be computationally infeasible to derive any useful information * about the input of SHA from its output.  Even if it is possible to * analyze SHA in some clever way, as long as the amount of data * returned from the generator is less than the inherent entropy in * the pool, the output data is totally unpredictable.  For this * reason, the routine decreases its internal estimate of how many * bits of "true randomness" are contained in the entropy pool as it * outputs random numbers. *  * If this estimate goes to zero, the routine can still generate * random numbers; however, an attacker may (at least in theory) be * able to infer the future output of the generator from prior * outputs.  This requires successful cryptanalysis of SHA, which is * not believed to be feasible, but there is a remote possibility. * Nonetheless, these numbers should be useful for the vast majority * of purposes. *  * Exported interfaces ---- output * =============================== *  * There are three exported interfaces; the first is one designed to * be used from within the kernel: * * 	void get_random_bytes(void *buf, int nbytes); * * This interface will return the requested number of random bytes, * and place it in the requested buffer. *  * The two other interfaces are two character devices /dev/random and * /dev/urandom.  /dev/random is suitable for use when very high * quality randomness is desired (for example, for key generation or * one-time pads), as it will only return a maximum of the number of * bits of randomness (as estimated by the random number generator) * contained in the entropy pool. *  * The /dev/urandom device does not have this limit, and will return * as many bytes as are requested.  As more and more random bytes are * requested without giving time for the entropy pool to recharge, * this will result in random numbers that are merely cryptographically * strong.  For many applications, however, this is acceptable. * * Exported interfaces ---- input * ============================== *  * The current exported interfaces for gathering environmental noise * from the devices are: *  * 	void add_keyboard_randomness(unsigned char scancode); * 	void add_mouse_randomness(__u32 mouse_data); * 	void add_interrupt_randomness(int irq); * 	void add_blkdev_randomness(int irq); *  * add_keyboard_randomness() uses the inter-keypress timing, as well as the * scancode as random inputs into the "entropy pool". *  * add_mouse_randomness() uses the mouse interrupt timing, as well as * the reported position of the mouse from the hardware. * * add_interrupt_randomness() uses the inter-interrupt timing as random * inputs to the entropy pool.  Note that not all interrupts are good * sources of randomness!  For example, the timer interrupts is not a * good choice, because the periodicity of the interrupts is to * regular, and hence predictable to an attacker.  Disk interrupts are * a better measure, since the timing of the disk interrupts are more * unpredictable. *  * add_blkdev_randomness() times the finishing time of block requests. *  * All of these routines try to estimate how many bits of randomness a * particular randomness source.  They do this by keeping track of the * first and second order deltas of the event timings. * * Ensuring unpredictability at system startup * ============================================ *  * When any operating system starts up, it will go through a sequence * of actions that are fairly predictable by an adversary, especially * if the start-up does not involve interaction with a human operator. * This reduces the actual number of bits of unpredictability in the * entropy pool below the value in entropy_count.  In order to * counteract this effect, it helps to carry information in the * entropy pool across shut-downs and start-ups.  To do this, put the * following lines an appropriate script which is run during the boot * 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 512 bytes, which is the size of the entropy pool * 	if [ -f $random_seed ]; then *		cat $random_seed >/dev/urandom * 	fi *	dd if=/dev/urandom of=$random_seed count=1 * 	chmod 600 $random_seed * * and the following lines in an appropriate script which is run as * the system is shutdown: *  *	# Carry a random seed from shut-down to start-up *	# Save 512 bytes, which is the size of the entropy pool *	echo "Saving random seed..." * 	random_seed=/var/run/random-seed *	dd if=/dev/urandom of=$random_seed count=1 * 	chmod 600 $random_seed *  * For example, on most modern systems using the System V init * scripts, such code fragments would be found in * /etc/rc.d/init.d/random.  On older Linux systems, the correct script * location might be in /etc/rcb.d/rc.local or /etc/rc.d/rc.0. *  * Effectively, these commands cause the contents of the entropy pool * to be saved at shut-down time and reloaded into the entropy pool at * start-up.  (The 'dd' in the addition to the bootup script is to * make sure that /etc/random-seed is different for every start-up, * even if the system crashes without executing rc.0.)  Even with * complete knowledge of the start-up activities, predicting the state * of the entropy pool requires knowledge of the previous history of * the system. * * Configuring the /dev/random driver under Linux * ============================================== * * The /dev/random driver under Linux uses minor numbers 8 and 9 of * the /dev/mem major number (#1).  So if your system does not have * /dev/random and /dev/urandom created already, they can be created * by using the commands: * * 	mknod /dev/random c 1 8 * 	mknod /dev/urandom c 1 9 *  * Acknowledgements: * ================= * * Ideas for constructing this random number generator were derived * from Pretty Good Privacy's random number generator, and from private * discussions with Phil Karn.  Colin Plumb provided a faster random * number generator, which speed up the mixing function of the entropy * pool, taken from PGPfone.  Dale Worley has also contributed many * useful ideas and suggestions to improve this driver. *  * Any flaws in the design are solely my responsibility, and should * not be attributed to the Phil, Colin, or any of authors of PGP. *  * The code for SHA transform was taken from Peter Gutmann's * implementation, which has been placed in the public domain. * The code for MD5 transform was taken from Colin Plumb's * implementation, which has been placed in the public domain.  The * MD5 cryptographic checksum was devised by Ronald Rivest, and is * documented in RFC 1321, "The MD5 Message Digest Algorithm". *  * Further background information on this topic may be obtained from * RFC 1750, "Randomness Recommendations for Security", by Donald * Eastlake, Steve Crocker, and Jeff Schiller. *//* * Added a check for signal pending in the extract_entropy() loop to allow * the read(2) syscall to be interrupted. Copyright (C) 1998  Andrea Arcangeli */#include <linux/utsname.h>#include <linux/config.h>#include <linux/kernel.h>#include <linux/major.h>#include <linux/string.h>#include <linux/fcntl.h>#include <linux/malloc.h>#include <linux/random.h>#include <linux/poll.h>#include <linux/init.h>#include <asm/processor.h>#include <asm/uaccess.h>#include <asm/irq.h>#include <asm/io.h>/* * Configuration information */#undef RANDOM_BENCHMARK#undef BENCHMARK_NOINT#define ROTATE_PARANOIA#define POOLWORDS 128    /* Power of 2 - note that this is 32-bit words */#define POOLBITS (POOLWORDS*32)/* * The pool is stirred with a primitive polynomial of degree POOLWORDS * over GF(2).  The taps for various sizes are defined below.  They are * chosen to be evenly spaced (minimum RMS distance from evenly spaced; * the numbers in the comments are a scaled squared error sum) except * for the last tap, which is 1 to get the twisting happening as fast * as possible. */#if POOLWORDS == 2048	/* 115 x^2048+x^1638+x^1231+x^819+x^411+x^1+1 */#define TAP1	1638#define TAP2	1231#define TAP3	819#define TAP4	411#define TAP5	1#elif POOLWORDS == 1024	/* 290 x^1024+x^817+x^615+x^412+x^204+x^1+1 *//* Alt: 115 x^1024+x^819+x^616+x^410+x^207+x^2+1 */#define TAP1	817#define TAP2	615#define TAP3	412#define TAP4	204#define TAP5	1#elif POOLWORDS == 512	/* 225 x^512+x^411+x^308+x^208+x^104+x+1 *//* Alt: 95 x^512+x^409+x^307+x^206+x^102+x^2+1 *      95 x^512+x^409+x^309+x^205+x^103+x^2+1 */#define TAP1	411#define TAP2	308#define TAP3	208#define TAP4	104#define TAP5	1#elif POOLWORDS == 256	/* 125 x^256+x^205+x^155+x^101+x^52+x+1 */#define TAP1	205#define TAP2	155#define TAP3	101#define TAP4	52#define TAP5	1#elif POOLWORDS == 128	/* 105 x^128+x^103+x^76+x^51+x^25+x+1 *//* Alt: 70 x^128+x^103+x^78+x^51+x^27+x^2+1 */#define TAP1	103#define TAP2	76#define TAP3	51#define TAP4	25#define TAP5	1#elif POOLWORDS == 64	/* 15 x^64+x^52+x^39+x^26+x^14+x+1 */#define TAP1	52#define TAP2	39#define TAP3	26#define TAP4	14#define TAP5	1#elif POOLWORDS == 32	/* 15 x^32+x^26+x^20+x^14+x^7+x^1+1 */#define TAP1	26#define TAP2	20#define TAP3	14#define TAP4	7#define TAP5	1#elif POOLWORDS & (POOLWORDS-1)#error POOLWORDS must be a power of 2#else#error No primitive polynomial available for chosen POOLWORDS#endif/* * For the purposes of better mixing, we use the CRC-32 polynomial as * well to make a twisted Generalized Feedback Shift Reigster * * (See M. Matsumoto & Y. Kurita, 1992.  Twisted GFSR generators.  ACM * Transactions on Modeling and Computer Simulation 2(3):179-194. * Also see M. Matsumoto & Y. Kurita, 1994.  Twisted GFSR generators * II.  ACM Transactions on Mdeling and Computer Simulation 4:254-266) * * Thanks to Colin Plumb for suggesting this. * We have not analyzed the resultant polynomial to prove it primitive; * in fact it almost certainly isn't.  Nonetheless, the irreducible factors * of a random large-degree polynomial over GF(2) are more than large enough * that periodicity is not a concern. * * The input hash is much less sensitive than the output hash.  All that * we want of it is that it be a good non-cryptographic hash; i.e. it * not produce collisions when fed "random" data of the sort we expect * to see.  As long as the pool state differs for different inputs, we * have preserved the input entropy and done a good job.  The fact that an * intelligent attacker can construct inputs that will produce controlled * alterations to the pool's state is not important because we don't * consider such inputs to contribute any randomness. * The only property we need with respect to them is * that the attacker can't increase his/her knowledge of the pool's state. * Since all additions are reversible (knowing the final state and the * input, you can reconstruct the initial state), if an attacker has * any uncertainty about the initial state, he/she can only shuffle that * uncertainty about, but never cause any collisions (which would * decrease the uncertainty). * * The chosen system lets the state of the pool be (essentially) the input * modulo the generator polymnomial.  Now, for random primitive polynomials, * this is a universal class of hash functions, meaning that the chance * of a collision is limited by the attacker's knowledge of the generator * polynomail, so if it is chosen at random, an attacker can never force * a collision.  Here, we use a fixed polynomial, but we *can* assume that * ###--> it is unknown to the processes generating the input entropy. <-### * Because of this important property, this is a good, collision-resistant * hash; hash collisions will occur no more often than chance. *//* * The minimum number of bits to release a "wait on input".  Should * probably always be 8, since a /dev/random read can return a single * byte. */#define WAIT_INPUT_BITS 8/*  * The limit number of bits under which to release a "wait on * output".  Should probably always be the same as WAIT_INPUT_BITS, so * that an output wait releases when and only when a wait on input * would block. */#define WAIT_OUTPUT_BITS WAIT_INPUT_BITS/* There is actually only one of these, globally. */struct random_bucket {	unsigned add_ptr;	unsigned entropy_count;#ifdef ROTATE_PARANOIA		int input_rotate;#endif	__u32 pool[POOLWORDS];};#ifdef RANDOM_BENCHMARK/* For benchmarking only */struct random_benchmark {	unsigned long long 	start_time;	int			times;		/* # of samples */	unsigned long		min;	unsigned long		max;	unsigned long		accum;		/* accumulator for average */	const char		*descr;	int			unit;	unsigned long		flags;};#define BENCHMARK_INTERVAL 500static void initialize_benchmark(struct random_benchmark *bench,				 const char *descr, int unit);static void begin_benchmark(struct random_benchmark *bench);static void end_benchmark(struct random_benchmark *bench);struct random_benchmark timer_benchmark;#endif/* There is one of these per entropy source */struct timer_rand_state {	__u32		last_time;	__s32		last_delta,last_delta2;	int		dont_count_entropy:1;};static struct random_bucket random_state;static struct timer_rand_state keyboard_timer_state;static struct timer_rand_state mouse_timer_state;static struct timer_rand_state extract_timer_state;static struct timer_rand_state *irq_timer_state[NR_IRQS];static struct timer_rand_state *blkdev_timer_state[MAX_BLKDEV];static struct wait_queue *random_read_wait;static struct wait_queue *random_write_wait;static ssize_t random_read(struct file * file, char * buf,			   size_t nbytes, loff_t *ppos);static ssize_t random_read_unlimited(struct file * file, char * buf,				     size_t nbytes, loff_t *ppos);static unsigned int random_poll(struct file *file, poll_table * wait);static ssize_t random_write(struct file * file, const char * buffer,			    size_t count, loff_t *ppos);static int random_ioctl(struct inode * inode, struct file * file,			unsigned int cmd, unsigned long arg);static inline void fast_add_entropy_words(struct random_bucket *r,					 __u32 x, __u32 y);static void add_entropy_words(struct random_bucket *r, __u32 x, __u32 y);#ifndef MIN#define MIN(a,b) (((a) < (b)) ? (a) : (b))#endif/* * Unfortunately, while the GCC optimizer for the i386 understands how * to optimize a static rotate left of x bits, it doesn't know how to * deal with a variable rotate of x bits.  So we use a bit of asm magic. */#if (!defined (__i386__))extern inline __u32 rotate_left(int i, __u32 word){	return (word << i) | (word >> (32 - i));	}#elseextern inline __u32 rotate_left(int i, __u32 word){	__asm__("roll %%cl,%0"		:"=r" (word)		:"0" (word),"c" (i));	return word;}#endif/* * More asm magic.... *  * For entropy estimation, we need to do an integral base 2 * logarithm.   * * Note the "12bits" suffix - this is used for numbers between

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -