LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Harry Prevor <habs@sdf.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Minifree Libreboot X220 libre laptop launched (pre-order)
Date: Fri, 17 Feb 2017 07:41:21 -0500	[thread overview]
Message-ID: <d7a3d0419108c98642ab28a60c59a5a5@sdf.org> (raw)
In-Reply-To: <f159b370-c398-aec8-30ef-d42da13e0eea@gluglug.org.uk>

(Apologies for the double post, if there was one.)

On 02/16/2017 01:52 PM, Leah Rowe wrote:
> Minifree has launched a new freedom-friendly laptop, with the free and
> open source Libreboot BIOS replacement, and Debian GNU+Linux
> preinstalled. This is the first modern laptop available with entirely
> libre software at every level, with no backdoors or rootkits like with
> the larger companies, and it's available on pre-order today.
> [...snip...]
> Here it is (more information is on the page):
> https://minifree.org/product/libreboot-x220/

When I saw the title of this post I was very excited, but since reading 
the nonchalant wording of the product description on the URL (which you 
curiously omitted from the announcement email) I'm now quite concerned.

The problem with this preorder is that there is no guarantee of freedom 
and it seems likely that various compromises will be made that 
compromise the freedom of the laptop and would therefore not qualify it 
for RYF certification.

A lot of people, myself included, would only want to pre-order this 
laptop if it was guaranteed that the Intel Management Engine would be 
fully disabled -- my understanding is that has been the #1 blocker for 
post-2009 Intel laptops for years now. However the website says, "If we 
fail in the above, then we will ship the X220 with a neutralized ME", 
telling me that the project is OK with shipping proprietary software if 
it is convenient to do so. If this compromise is made, I do not think 
this laptop should qualify for RYF certification.

I am not sure what the FSF's stance is on whether CPU microcode updates 
are considered firmware, but obviously it would be ideal to have a 
guarantee of the removal of those as well, which is also not provided in 
the product description.

As such, if no progress is made in these two regards, which the preorder 
page leaves open as a possibility, I think it would be defrauding all 
the users who preordered expecting an RYF-certified laptop.

---
Harry Prevor


  parent reply	other threads:[~2017-02-17 12:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b39232f4-7e49-137a-0d53-1315db513aec@gluglug.org.uk>
2016-12-16  3:13 ` please promote the TALOS libre workstation Leah Rowe
2016-12-30  6:48 ` Minifree Libreboot D16 server/workstation launched Leah Rowe
     [not found] ` <f159b370-c398-aec8-30ef-d42da13e0eea@gluglug.org.uk>
     [not found]   ` <399AB471-A746-4F6F-AC8D-8E0F2331F26B@mes3hacklab.org>
2017-02-17 10:02     ` Minifree Libreboot X220 libre laptop launched (pre-order) Leah Rowe
2017-02-17 11:07   ` Harry Prevor
2017-02-17 11:24     ` Harry Prevor
2017-02-17 12:41   ` Harry Prevor [this message]
2018-04-30 13:34 ` Call for reviews: Libreboot X200 Tablet on Minifree (FSF RYF pending) Leah Rowe
2018-05-01 20:14   ` minifree.org is blocked from access by CDN’s nonfree software Dmitry Alexandrov
2018-05-01 20:47     ` Leah Rowe
2018-05-01 20:53       ` Leah Rowe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d7a3d0419108c98642ab28a60c59a5a5@sdf.org \
    --to=habs@sdf.org \
    --cc=libreplanet-discuss@libreplanet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).