Yeah, @Puri_sm do good work, but they are unfortunately held back by their goal of wanting to get FSF "Respects your Freedom" certification (which does anything but). I've ranted about this on Twitter before. They are having to engineer horrible anti-user hacks to meet it.
-
-
Replying to @marcan42 @justinrwlynn and
On a more positive note, a couple of times I've basically said "nobody does open X", someone said "
@RaptorEng do" and@RaptorEng immediately followed up with a Git repo link. <31 reply 0 retweets 6 likes -
Replying to @marcan42 @justinrwlynn and
Sigh...over-exaggerating is a nice way to say false advertisement. They will /never/ be able to deliver a libreboot machine, and the first machines they shipped delivered on none of their promises. They admittedly do a great job with UI and education for secure computing.
1 reply 0 retweets 2 likes -
Replying to @RobertSpigler @marcan42 and
They're working on a dead platform, I wish they'd see that. They have to reverse engineer each gen. of CPU to partially free it of IntelME (which they'll then advertise as fully free), so the machines will always be years behind. And with Blackbird's out, they're not cheaper.
2 replies 0 retweets 2 likes -
Replying to @RobertSpigler @justinrwlynn and
I was mostly thinking of their phone, which has a decent chance of getting close to fully free (as far as the AP goes anyway) but the way they're dealing with the remaining blobs is deliberately *anti-freedom* because that's what RYF certification requires.
1 reply 0 retweets 2 likes -
Replying to @marcan42 @RobertSpigler and
Basically the FSF says if you make blobs invisible, immutable, un-auditable, and therefore un-freeable then they might as well not exist by their definition, which is hilariously backwards - I want all my blobs in /lib/firmware where I can see them and mess with them.
2 replies 0 retweets 6 likes -
Replying to @marcan42 @RobertSpigler and
FSF guys might not fully understand what libre firmware means.
@Puri_sm has done some good job to make skylake-based machine as "libre" as possible. But some parts of x86 e.g: microcode, ME/SGX can't be audited in nature stops anyone who try to go further to build the libre fw.2 replies 0 retweets 1 like -
I'm not too upset about the
#Librem Laptops, there they are doing the best they can AFAIK. They even did some reverse engineering of ME ROMP:https://puri.sm/posts/reverse-engineering-the-intel-management-engine-romp-module/ …1 reply 0 retweets 0 likes -
Replying to @olddellian @citypw and
and of the FSP, although some of that info was taken down at
@intel's demand: https://puri.sm/posts/intel-fsp-reverse-engineering-finding-the-real-entry-point/ …1 reply 0 retweets 0 likes -
Replying to @olddellian @citypw and
but
@marcan42 was talking about the#Librem5, where@Puri_sm team decided to use the "secondary processor" loophole in the RYF requirements to load a proprietary blob anyway, but hide it from the user and waste an entire CPU core: https://puri.sm/posts/librem5-solving-the-first-fsf-ryf-hurdle/ …2 replies 0 retweets 0 likes
And as far as I can tell they did this with the full blessing of the FSF. The entire "secondary processor" loophole is a terribly ill-conceived backdoor designed to make non-fully-libre systems *appear to be* libre while in fact they are more evil than just loading a normal blob.
-
-
Replying to @marcan42 @olddellian and
I'm *okay* with blobs - they're not ideal, but they're a fact of life on most systems, and at least we can analyze them. I am *not okay* with the FSF actively trying to hide blobs from me, and then claiming it's 100% free.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.