This bootloader is like a much simpler version of GRUB/Elilo/Windows Boot Manager, but mainly meant for writing your own operating system-less 64-bit programs, kernels, or full operating systems. It supports Windows, Linux, and Mac executable binaries (PE32+, 64-bit ELF, and 64-bit Mach-O formats). It also supports… Well, I’ll let you figure that one out yourself. 😉 […]

https://github.com/KNNSpeed/Simple-UEFI-Bootloader

See-also:

https://github.com/KNNSpeed/Simple-Kernel/

[They’re talking about NXP (Freescale) i.MX6 Secure Boot.]

Nathan Padoin | Jan 29, 2018

Data security is more important than ever with the avalanche of connected devices, and implementing Secure Boot is a crucial step in making it happen.[…]

https://www.electronicdesign.com/embedded-revolution/secure-boot-what-you-need-know

https://twitter.com/fatihyuksektepe/status/1097489713177477120

https://www.cyberciti.biz/faq/how-to-find-intel-nuc-bios-version-and-model-on-linux/

The inherent nature of firmware makes it an appealing target for hackers as the hardening of traditional exploit vectors (e.g., operating systems and the applications) is leading to new routes of attack. Join the UEFI Forum Secure Coding webinar to hear the panel of security experts discuss tips and best practices.

Moderator:
Brian Richardson, Intel Corporation

Panelists:
Dick Wilkins, Phoenix Technologies
Trevor Western, Insyde Software
Eric Johnson, American Megatrends Inc.

https://register.gotowebinar.com/register/8562801240869758977

https://uefi.org/

Re: https://firmwaresecurity.com/2018/11/04/upos-info-latency-throughput-and-port-usage-information-for-instructions-on-recent-intel-microarchitectures/

nanoBench is a Linux-based tool for running small microbenchmarks on recent Intel and AMD x86 CPUs. The microbenchmarks are evaluated using hardware performance counters. The reading of the performance counters is implemented in a way that incurs only minimal overhead. There are two variants of the tool: A user-space implementation and a kernel module. The kernel module makes it possible to benchmark privileged instructions, and it can allow for more accurate measurement results as it disables interrupts and preemptions during measurements. The disadvantage of the kernel module compared to the user-space variant is that it is quite risky to allow arbitrary code to be executed in kernel space. Therefore, the kernel module should not be used on a production system. nanoBench is used for running the microbenchmarks for obtaining the latency, throughput, and port usage data that is available on uops.info.

https://github.com/andreas-abel/nanoBench

http://uops.info/

RAVENS (Resilient Architecture for Very Efficient firmware updates of Network-connected Systems) is a software ecosystem built on top of two main components, Hugin and Munin. […] Properly used, Hugin and Munin enable secure and efficient firmware updates of very small IoT devices.

https://github.com/Orange-OpenSource/RAVENS

https://docs.google.com/presentation/d/1z-giB9kom17Lk21YEjmceiNUVYeI6yIaG5_gZ3vKC-M/edit#slide=id.g1925acbbf3_0_0

https://twitter.com/jessfraz/status/1095244333689667584

https://erfur.github.io/down_the_rabbit_hole_pt1/

https://erfur.github.io/down_the_rabbit_hole_pt2/

Mesos is a tool to gather binary code coverage on all user-land Windows targets without need for source or recompilation. It also provides an automatic mechanism to save a full minidump of a process if it crashes under mesos. Mesos is technically just a really fast debugger, capable of handling tens of millions of breakpoints. Using this debugger, we apply breakpoints to every single basic block in a program. These breakpoints are removed as they are hit. Thus, mesos converges to 0-cost coverage as gathering coverage only has a cost the first time the basic block is hit.

https://github.com/gamozolabs/mesos

CompareCoverage (CmpCov in short) is a simple instrumentation module for C/C++ programs and libraries, which extracts information about data comparisons taking place in the code at run time, and saves it to disk in the form of standard .sancov files. It is based on the SanitizerCoverage instrumentation available in the clang compiler, which itself is tightly related to AddressSanitizer. Specifically, the library implements the instrumentation callbacks defined by the Tracing data flow feature of SanitizerCoverage.

https://github.com/googleprojectzero/CompareCoverage

Re: https://firmwaresecurity.com/2019/01/22/raymond-chen-the-intel-80386-blog-series/

https://blogs.msdn.microsoft.com/oldnewthing/20190212-00/?p=100915

Wow, this new blog series is up to 17-parts now!