HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
htruong
ezpi4me
Shell2018–2018
htruong / ezpi4me

ezpi4me

Raspberry Pi-based me-cleaner and libre firmware for dummies.

2Distinct people
3Mentions
0Explicit recommenders
30GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Raspberry Pi-based me-cleaner and libre firmware for dummies.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day3 dated mentions

Observed mentions: 2018-02-14 23:39:57 UTC to 2018-02-22 18:38:18 UTC.

012018-02-14 00:00:00 UTC to 2018-02-15 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 142018-02-15 00:00:00 UTC to 2018-02-16 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-02-16 00:00:00 UTC to 2018-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-17 00:00:00 UTC to 2018-02-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-18 00:00:00 UTC to 2018-02-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 182018-02-19 00:00:00 UTC to 2018-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-20 00:00:00 UTC to 2018-02-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-21 00:00:00 UTC to 2018-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-22 00:00:00 UTC to 2018-02-23 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 22

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 142018-02-14 00:00:00 UTC2018-02-15 00:00:00 UTC110
Feb 152018-02-15 00:00:00 UTC2018-02-16 00:00:00 UTC101
Feb 162018-02-16 00:00:00 UTC2018-02-17 00:00:00 UTC000
Feb 172018-02-17 00:00:00 UTC2018-02-18 00:00:00 UTC000
Feb 182018-02-18 00:00:00 UTC2018-02-19 00:00:00 UTC000
Feb 192018-02-19 00:00:00 UTC2018-02-20 00:00:00 UTC000
Feb 202018-02-20 00:00:00 UTC2018-02-21 00:00:00 UTC000
Feb 212018-02-21 00:00:00 UTC2018-02-22 00:00:00 UTC000
Feb 222018-02-22 00:00:00 UTC2018-02-23 00:00:00 UTC101

What Hacker News says

3 sources
Welcome to the bright side. I've been enjoying my Chromebook with coreboot and nerf'ed Intel ME for years. It's not as hard as many of us would think. By the way, Chromebooks are cheap and is a fantastic platform to experiment with coreboot/de-intel-ME. Acer C720s are $100 right now. There are 2 spererate tasks: Flashing coreboot and De-blob'ing Intel ME. If you just want to try coreboot with the Chromebook, then you can do it with software and don't need an external programmer. All you have to do is just remove the BIOS write-protect screws - MrChromebox's website is a great resource. If you need to de-blob the chromebooks, then you'd need an external programmer, such as a Raspberry Pi. As a shameless plug, I have released a tool so one doesn't have to be an electrical engineer and/or a Linux expert to flash many Chromebooks/Thinkpads wi
Read the rest
th a Raspberry Pi [1]. You don't really have to have a breadboard to flash the Chromebooks like you do with the Thinkpad in the article. Also, the cool thing about it is that it prepares the image on your x86 computer so you literally don't have to configure the pi and get/compile stuff afterwards. I didn't know that the X200 needs a patch. I will integrate the x200 support into ezpi4ME so people don't have to manually patch and wait for it to compile on the Pi. 1: github.com/htruong/EzPi4ME Edit: I noticed OP has a blog post complaining about Acer 720s having problems. It hasn't happened to me, at least with MrChromebox's firmware. I did have problem with John Lewis' firmware builds, though.
In Liberating a X200
What a coincidence. Just today, I released the project that I've been holding off for more than a year: Basically, it is a distro [1] for the Raspberry Pi that sole purpose is to clean the Intel ME automatically using me-cleaner from Chromebooks and Thinkpads. The whole idea is to make it dead simple so more and more people can DIY the ME removal process with their own laptop/desktop. I thought to myself, it's nice to not have the problem in the first place. It won't help you with certain problems such as Spectre, no, but reducing the surface of attack is not a silly thing. There are things you can't avoid even with the best intentions. But there are things that you can. The name of it is ezpi4me [2]. Of course, it's pretty experimental. You might not want to experiment with it (yet?). It's not very practical, yet, for an inexperienced in
Read the rest
dividual to open a laptop, risk bricking by fiddling with a flash chip. I put a lot of thoughts in it before I decided to release this. To me personally, it's more of a symbolism/a protest than it's practical. The project is the inner me saying, maybe instead of complaining, I'd have to get up my butt and do a tiny thing to help the cause I believe in. I despise the practice of shoving mandatory opaque, backdoor binary blobs to their hardware -- and incentivizing people from saying their shitty binary blobs have security problems by offering hackers/security researchers a shitload of money so they shut up and cooperate. What it entails is that what can be bought by a lot of money from Intel can be bought by even more money from other people. It really rustles my jimmies. We'd have to start somewhere. Perhaps a year from now, someone will figure out an even easier, better way to achieve the same result. Or perhaps, it will be easy enough to the point that some guys on eBay/Amazon/brick and mortar stores will use my software to clean the ME from laptops they sell en-masse as a factor of differentiation. I hope it will be another step up in terms of usability and adoption from me_cleaner. With that hope, I'm just donating a couple of sleepless nights of my life working on a software that might jeopardize my career and make a lot of people upset. But fuck all that, I'm doing it anyway, for once I can say I'm the change that I want to see. -- 1: Technically, it's just a script to create a distro based on raspbian lite, so everything can be inspected. That is on purpose because I don't want to advocate replacing the 3MB Intel ME blob with jimmies' blob, which is a 2GB image that you run on your Pi and program your computer's UEFI firmware/BIOS. 2: https://github.com/htruong/ezpi4me/
In Intel Expands Bug Bounty Program

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.