opnsense-src/sys/modules/random/Makefile

# $FreeBSD$

.PATH: ${.CURDIR}/../../dev/random
.PATH: ${.CURDIR}/../../crypto/rijndael
.PATH: ${.CURDIR}/../../crypto/sha2

KMOD=	random
SRCS=	randomdev.c
.if ${MACHINE} == "amd64" || ${MACHINE} == "i386"
SRCS+=	nehemiah.c
SRCS+=	ivy.c
.endif
SRCS+=	randomdev_soft.c yarrow.c hash.c
SRCS+=	random_harvestq.c live_entropy_sources.c rwfile.c
SRCS+=	rijndael-alg-fst.c rijndael-api-fst.c sha2.c sha256c.c
SRCS+=	bus_if.h device_if.h vnode_if.h opt_cpu.h opt_random.h

CFLAGS+= -I${.CURDIR}/../..

.include <bsd.kmod.mk>
Build the entropy device (/dev/random) as a module. This may not be a permanent rule, because this device may eventually be deemed "effectively compulsory", and built by default directly into the kernel. For the moment, however, this is useful for debugging and development. Reviewed by: dfr 2000-06-25 06:12:33 -04:00			`# $FreeBSD$`

Use a consistent style and one much closer to the rest of /usr/src 2001-01-06 09:00:42 -05:00			`.PATH: ${.CURDIR}/../../dev/random`
Back out r253779 & r253786. 2013-07-31 13:21:18 -04:00			`.PATH: ${.CURDIR}/../../crypto/rijndael`
			`.PATH: ${.CURDIR}/../../crypto/sha2`
Use a consistent style and one much closer to the rest of /usr/src 2001-01-06 09:00:42 -05:00
			`KMOD= random`
1) example (partially humorous random_adaptor, that I call "EXAMPLE") * It's not meant to be used in a real system, it's there to show how the basics of how to create interfaces for random_adaptors. Perhaps it should belong in a manual page 2) Move probe.c's functionality in to random_adaptors.c * rename random_ident_hardware() to random_adaptor_choose() 3) Introduce a new way to choose (or select) random_adaptors via tunable "rngs_want" It's a list of comma separated names of adaptors, ordered by preferences. I.e.: rngs_want="yarrow,rdrand" Such setting would cause yarrow to be preferred to rdrand. If neither of them are available (or registered), then system will default to something reasonable (currently yarrow). If yarrow is not present, then we fall back to the adaptor that's first on the list of registered adaptors. 4) Introduce a way where RNGs can play a role of entropy source. This is mostly useful for HW rngs. The way I envision this is that every HW RNG will use this functionality by default. Functionality to disable this is also present. I have an example of how to use this in random_adaptor_example.c (see modload event, and init function) 5) fix kern.random.adaptors from kern.random.adaptors: yarrowpanicblock to kern.random.adaptors: yarrow,panic,block 6) add kern.random.active_adaptor to indicate currently selected adaptor: root@freebsd04:~ # sysctl kern.random.active_adaptor kern.random.active_adaptor: yarrow Submitted by: Arthur Mesh <arthurmesh@gmail.com> 2013-08-24 09:54:56 -04:00			`SRCS= randomdev.c`
Back out r253779 & r253786. 2013-07-31 13:21:18 -04:00			`.if ${MACHINE} == "amd64" \|\| ${MACHINE} == "i386"`
			`SRCS+= nehemiah.c`
			`SRCS+= ivy.c`
			`.endif`
			`SRCS+= randomdev_soft.c yarrow.c hash.c`
Add needed files to the KLD random.ko. Approved by: re (kib) 2013-10-14 13:43:22 -04:00			`SRCS+= random_harvestq.c live_entropy_sources.c rwfile.c`
I clearly didn't test the modules... add sha256c.c to the various modules that included sha2.c... 2014-03-15 21:55:30 -04:00			`SRCS+= rijndael-alg-fst.c rijndael-api-fst.c sha2.c sha256c.c`
Add YARROW_RNG and FORTUNA_RNG to sys/conf/options. Add a SYSINIT that forces a reseed during proc0 setup, which happens fairly late in the boot process. Add a RANDOM_DEBUG option which enables some debugging printf()s. Add a new RANDOM_ATTACH entropy source which harvests entropy from the get_cyclecount() delta across each call to a device attach method. 2013-10-08 07:05:26 -04:00			`SRCS+= bus_if.h device_if.h vnode_if.h opt_cpu.h opt_random.h`
Back out r253779 & r253786. 2013-07-31 13:21:18 -04:00
			`CFLAGS+= -I${.CURDIR}/../..`
Build the entropy device (/dev/random) as a module. This may not be a permanent rule, because this device may eventually be deemed "effectively compulsory", and built by default directly into the kernel. For the moment, however, this is useful for debugging and development. Reviewed by: dfr 2000-06-25 06:12:33 -04:00
			`.include <bsd.kmod.mk>`