Kyle Rankin c99d5a8437

Add red background to boot console for insecure "force" boot ...

In the event a user does pick the insecure "force" boot option that
bypasses checksum and signing checks in Heads, it would be nice to
provide a clear visual warning during the boot process that they are in
this state. This change will add a kernel argument that changes the boot
console background to be red and removes any boot splash that might
obscure it, in the event the user picks the insecure boot mode.

Since a user should only boot into this mode during emergencies, having
it be apparent that it's an unsafe mode helps ensure the user doesn't
pick this boot option needlessly.

2018-04-11 16:09:46 -07:00

..

.gnupg

hardware token key

2017-04-12 09:50:08 -04:00

.ssh

enable qemu networking and ssh key login (#312)

2018-02-09 13:42:52 -05:00

bin

Add red background to boot console for insecure "force" boot

2018-04-11 16:09:46 -07:00

etc

enable setsid for job control in recovery shell (issue #382)

2018-04-10 15:39:05 -04:00

sbin

"$@" does not expand correctly in test expressions, use "$*" instead (issue #181)

2017-04-11 06:31:25 -04:00

.ash_history

preload the recovery shell command line history

2016-09-26 13:51:10 -04:00

init

Moved network init to a separate bootscript

2018-03-10 15:40:07 -08:00

mount-boot

extract and verify gpg signature on the boot script

2016-08-06 17:13:22 -04:00