en Copyright 2015 Java http://172.16.0.5:8080/history/freebsd-13.1/libexec/rc/rc.d/random#26c49788 save-entropy(8), rc.d/random: Set nodump flagTag saved entropy files as "nodump," to signal that the files should not bebacked up by dump(8) or other automated backup software that honors the fileflag.Do not produce an error if the target file resides on a filesystem that doesnot support file flags (e.g., msdos /boot).Reviewed by: delphijSponsored by: Dell EMC IsilonDifferential Revision: https://reviews.freebsd.org/D20358 List of files: /freebsd-13.1/libexec/rc/rc.d/random Wed, 22 May 2019 21:47:17 +0000 Conrad Meyer <cem@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-13.1/libexec/rc/rc.d/random#c849485d random(4): Attempt to persist entropy promptlyThe goal of saving entropy in Fortuna is two-fold: (1) to provide earlyavailability of the random device (unblocking) on next boot; and (2), tohave known, high-quality entropy available for that initial seed. We knowit is high quality because it's output taken from Fortuna.The FS&K paper makes it clear that Fortuna unblocks when enough bits havebeen input that the output //may// be safely seeded. But they emphasizethat the quality of various entropy sources is unknown, and a saved entropyfile is essential for both availability and ensuring initialunpredictability.In FreeBSD we persist entropy using two mechanisms:1. The /etc/rc.d/random shutdown() function, which is used for ordinary shutdowns and reboots; and,2. A cron job that runs every dozen minutes or so to persist new entropy, in case the system suffers from power loss or a crash (bypassing the ordinary shutdown path).Filesystems are free to cache dirty data indefinitely, with arbitrary flushpolicy. Fsync must be used to ensure the data is persisted, especially forthe cron job save-entropy, whose entire goal is power loss and crash safeentropy persistence.Ordinary shutdown may not need the fsync because unmount should flush outthe dirty entropy file shortly afterwards. But it is always possible powerloss or crash occurs during the short window after rc.d/random shutdown runsand before the filesystem is unmounted, so the additional fsync there seemsharmless.PR: 230876Reviewed by: delphij, markj, markmApproved by: secteam (delphij)Differential Revision: https://reviews.freebsd.org/D19742 List of files: /freebsd-13.1/libexec/rc/rc.d/random Sun, 31 Mar 2019 04:57:50 +0000 Conrad Meyer <cem@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-13.1/libexec/rc/rc.d/random#0696600c Move the rc framework out of sbin/init into libexec/rc.The reasons for this are forward looking to pkgbase: * /sbin/init is a special binary; try not to replace it with every package update because an rc script was touched. (a follow-up commit will make init its own package) * having rc in its own place will allow more easy replacement of the rc framework with alternatives, such as openrc.Discussed with: brd (during BSDCam), kmooreRequested by: cem, bzPR: 231522Approved by: re (gjb) List of files: /freebsd-13.1/libexec/rc/rc.d/random Wed, 17 Oct 2018 16:49:11 +0000 Bjoern A. Zeeb <bz@FreeBSD.org>