Hello, On 1/20/20 8:53 PM, Sascha Hauer wrote: > Disabling the shell entirely with CONFIG_SHELL_NONE is the best you can > do. This also forces you to program your boot process in C which helps > you to get a well defined boot without diving into potentially unsafe > shell commands. > > To state the obvious, you have to enable HAB support, sign your barebox > images and burn the necessary fuses to forbid loading unsigned images. I think it would be great to have a CONFIG_LOCKDOWN option that has inverse dependencies on the stuff that should not be enabled and normal dependencies on the stuff that should be. Such a CONFIG_LOCKDOWN barebox can then be used in secure boot scenarios or for fuzzing efforts. Thoughts? > > Sascha > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
