Windows-centric project. Quoting all of the documentation, for anything else, see the sources:
“A Small and simple UEFI SDK which provides the most common protocols and a small library (printf etc)”
Windows-centric project. Quoting all of the documentation, for anything else, see the sources:
“A Small and simple UEFI SDK which provides the most common protocols and a small library (printf etc)”
Tweets from CopperheadOS, a security-centric Android-based distribution, are a good source of Android security news, since they’re stretching the boundaries of the open source android release.
Liberating Bootloaders and Cellular Modem Firmware of MediaTek Phones
As a community project, and one that encourages contributors to work on what they like, we have attracted people with a broad range of interests and skill levels. Recently a small hacking group #postmarketOS-lowlevel has emerged, and its masterminds @McBitter and @unrznbl are eager to introduce you to the madness that awaits when digging deeper and deeper in the embedded hardware and software stack. But before we get started, please keep in mind that these are moon shots. So while there is some little progress, it’s mostly about letting fellow hackers know what we’ve tried and what we’re up to, in the hopes of attracting more interested talent to our cause. After all, our philosophy is to keep the community informed and engaged during the development phase! For those new to postmarketOS, we are a group of developers, hackers, and hobbyists who have come together with a common goal of giving a ten year life cycle to mobile phones. This is accomplished by using a simple and sustainable architecture borrowed from typical Linux distributions, instead of using Android’s build system. The project is at an early stage and isn’t useful for most people at this point. Check out the newly-updated front page for more information, the previous blog post for recent achievements, and the closed pull requests to be informed about what’s going on up to the current minute. Let’s dive in!
https://postmarketos.org/blog/2018/04/14/lowlevel/
https://github.com/postmarketOS/
https://wiki.postmarketos.org/wiki/Devices
https://github.com/PreOS-Security/awesome-firmware-security/blob/master/README.md
This is the initial version of the awesome-firmware-security list! I’ve been putting this off for a while (since day 2 of this blog), luckily Paul did most of the work to release this. Thanks, Paul!
If this initial release smells like a Glossary for an ebook, there’s a reason for that: we have an upcoming ebook, and this initial release of this list was meant to act as More Info and Glossary for the ebook. 🙂
This is scoped to platform security, for security researchers, DFIR, Blue Team, SysAdmins, etc. Currently it is focused mostly on Platform Firmware (eg, UEFI). It needs help from others that’re focusing on IoT/embedded/mobile device ‘firmware’.
I’ll have a second list for firmware development-centric topics in near future.
There’s MANY things to add. Please submit a patch with more details, I’m hoping this is a community effort, not just Paul and I adding entries to this list. PLEASE HELP!
WASHINGTON, April 12, 2018 /PRNewswire/ — Today, the Center for Cybersecurity Policy and Law announced a new cybersecurity effort to examine coordinated vulnerability disclosure policy and processes specific to hardware.
Coordinated disclosure is widely regarded as the best way to responsibly protect users from security exploits. Led by Ari Schwartz, the Center’s coordinator, the project will bring together business leaders, policymakers and other stakeholders from across the technology sector to identify specific disclosure needs in the hardware ecosystem, assess the current in disclosure policy and practice and describe options for collaboration and improvements. “As recent threats have shown, the need for industrywide coordination and response to new vulnerabilities has never been greater,” said Schwartz. “We are looking forward to engaging with a wide range of players to help improve resiliency in the hardware ecosystem.” […]
https://centerforcybersecuritypolicy.org/
What about the other chip makers beyond Intel?
Nikolaj is learning Rust. He just rewrote one C tool to Rust:
Command Line EFI Mounter
This is a simple app that helps you to mount any EFI partition Inside Mac OS X.
Working for Mac OS X 10.9 to 10.13
https://github.com/chris1111/Command-Line-EFI-Mounter
This repo contains the tools to build images to run CI for the Red Hat bootloader team’s EFI tools. This build includes all of the dependencies of the build as well as the testing infrastructure, to minimize the time spent per Travis build. Each repo has a .travis.yml will install this docker image, fetch and build any prerequisites, and build that repo using whatever branch travis specifies.
Intel has 2 new Persistent Memory updates last month, a new dev kit and a white paper on the topic:
https://software.intel.com/en-us/videos/persistent-memory-programming-tools
The Persistent Memory Development Kit (PMDK), formerly known as NVML, is a growing collection of libraries which have been developed for various use cases, tuned, validated to production quality, and thoroughly documented.

Spectre Mitigation Update
4/10/18
Today, AMD is providing updates regarding our recommended mitigations for Google Project Zero (GPZ) Variant 2 (Spectre) for Microsoft Windows users. These mitigations require a combination of processor microcode updates from our OEM and motherboard partners, as well as running the current and fully up-to-date version of Windows. For Linux users, AMD recommended mitigations for GPZ Variant 2 were made available to our Linux partners and have been released to distribution earlier this year.[…]
https://www.amd.com/en/corporate/security-updates
Click to access Architecture_Guidelines_Update_Indirect_Branch_Control.pdf
https://www.amd.com/en/corporate/security-updates#paragraph-347856
The below articles point to related tools, besides the Hak5 Rubber Ducky.
https://github.com/mharjac/bad_ducky
https://twitter.com/anonymous9396/status/983165816160972806
https://www.kitploit.com/2018/04/bad-ducky-rubber-ducky-compatible-clone.html
See-also:
https://ducktoolkit.com/viewscript/all/
https://github.com/hak5darren/USB-Rubber-Ducky/wiki/Payloads

[[UPDATE: It appears uefi.tech has changed their policy regarding scraping list postings. They have updated their site.]]
Re: https://firmwaresecurity.com/2018/04/09/new-uefi-centric-web-site-uefi-tech-uefitech/
I don’t know who is behind this new UEFI web site. The site is scraping postings from the UEFI Forum’s public mailing list, FW_OS_Forum and adding them to their web board, automatically adding the poster to their site, making it look like people who are posting to the FW_OS_Forum list are also posting on the uefi.tech forum.
For example:
http://lists.mailman.uefi.org/pipermail/fw_os_forum/20180409/000068.html
http://www.uefi.tech/viewtopic.php?f=9&t=11&p=67&sid=cfcbd9ed0310915eaf2e397f1b978e8f#p67
Minnowboard Turbot remote firmware flashing with RTE (Remote Testing Environment)
April 5, 2018
Arek Cichocki
Work related to a hardware carries some restrictions which don’t occur when working only with a software. One of them is a limited number of devices. This one may cause a problem with a accessibility to the platform. The limited number of users could slow development and testing. What is more work with a hardware requires a minimal knowledge of the theory of circuits and signals to eliminate platform damage by a user. Hardware can be expensive too. Remote Testing Environment project was made to resolve mentioned problems. […]

Re: https://firmwaresecurity.com/2018/03/15/scaleway-open-source-bios-at-scale/
A look from behind the Open Source Bios
This is a followup post of Open Source Bios at Scale so you might want to read it first as this post will get more into details. As explained in the previous post our BIOS is build with three main components: coreboot, Intel FSP and TianoCore. We will describe here how those three parts are fitting together.[…]
https://blog.online.net/2018/04/10/a-look-from-behind-the-open-source-bios/
Megha Dey of Intel has announced the latest release of LUV, with multiple new features and bugfixes by multiple contributors:
Gayatri Kammela (12), Megha Dey (9), Naresh Bhat (3), Ricardo Neri (22), Sai Praneeth (5)
It mostly includes updates to yocto, meta-oe, various test suites and kernel version and bug fixes. We have also added a feature to display the severity of failed test cases. Since we had the stable v2.2 release 2 months back, it made sense to have this release as rc1 of v2.3 to allow stabilization towards the next release cycle.
Main new feature: Display the severity of failed test cases In this release, Ricardo submitted 2 patchsets to display the severity of failed test cases. This is a valuable addition as LUV now ships with 7 different test suites. Some test suites include hundreds of test cases. Thus, we could possibly have tens of failed test cases, which can be overwhelming. In order to help users to decide on which failed test cases focus their attention, it is useful to indicate the severity of failed test cases.
See the full announcement for list of bugfixes.
https://download.01.org/linux-uefi-validation/v2.3/
https://lists.01.org/mailman/listinfo/luv
https://github.com/johkra/efi-undervolt
Microsoft-centric:
#define LOADER L“\\EFI\\Microsoft\\Boot\\bootmgfw.efi“
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Discover the Desktop
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
News from coreboot world
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Just another WordPress.com site
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
You must be logged in to post a comment.