unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Cc: guix-devel <guix-devel@gnu.org>,
	Workgroup for fully free GNU/Linux distributions
	<gnu-linux-libre@nongnu.org>
Subject: Re: [GNU-linux-libre] Free firmware - A redefinition of the term and a new metric for it's measurement.
Date: Tue, 14 Feb 2017 19:43:48 +0100	[thread overview]
Message-ID: <CAL1_imnD_xpiWrWQvXgD_Qp2qLV3aNZ8W+xdk0F8tXabBVeoQw@mail.gmail.com> (raw)
In-Reply-To: <20170214131548.35dafcfc@second-laptop>

Hi Denis,

Thank you for your extensive feedback.

> With that we can still use WiFi by ignoring the intel wifi card and
> using an USB wifi card instead.

I considered using this option but realized that I had a buggy thunderbolt
controller in my laptop, that I can only update from a windows computer
and therefore know for sure it can be modified remotely poses a much
larger security issue, that I would not actually gain anything from replacing
my wifi card. And besides these obvious and visible firmwares I have no
clue what other non-free firmware is running on my laptop.

I concluded that if I didn't know, that likely most linux-libre users didn't
know either and where likely much less aware of what that could actually
mean.

While obviously you understand hardware and the hardware you are
using, most people do not. And I think we need to make sure that
people that don't - I consider myself being one of those people - can do
the *best* with what we have and have the information available to us
to make informed decisions.

I bought my dell xps developer edition before I had any involvement
with a GNU project, and I bought it because dell was actually providing
at least some kind of linux support. I currently can't afford to buy a new
laptop even if the one you are using is much more free. Besides I have
the dream of building a replacement mainboard with a RISCV SoC for
it. But that is still beyond my capabilities :) FYI: This dream mainboard
would also feature a software defined radio [0] instead of a wifi card -
another interesting free hardware project, although the sources have
not been released yet.


Another thing I found very frustrating was a conversation that I had
on IRC. It went like this:

Can guixsd run on a RPiv2?

Yes, sure. You'll need to use vanilla linux and add some firmware, I'll
show you how to do it.

No thank you. I don't want to use binary blobs. I'll just use another
distro until guixsd works without binary blobs.

I expect that everyone recognizes the irony in that.

> While this is really great and that each new free firmware is a great
> achievement

I agree.

> When taking security seriously, the fact that a non-free firmware is
> running in peripherals that can have access to the main system's RAM
> has to be taken into account.
>
> However I don't have a clear idea on whether it has to be dealt with
> within free software policies or not, and how much it is in the scope
> of free software.
>
> I don't think we, as the free software community, can ignore it as it
> means that some non-free code can take control of your computer...

Yes with buggy thunderbolt controllers this is becoming a real problem.

> For instance in Replicant, we decided not to focus on devices that can
> permit non-free firmwares to take control of the main processor, and
> instead to prioritize work on devices where the hardware doesn't have
> any physical ways to allow a non-free firmware to access the main
> processor's RAM.

Replicant looks very interesting, especially since I owned quite a few of
those nexus devices that are supported. Sadly not anymore :/

I wasn't aware that there was so much documentation available about
mobile devices. How do you know all that stuff? :)

Thank you for your input,
David

[0] https://xtrx.io/

  reply	other threads:[~2017-02-14 18:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 14:37 Free firmware - A redefinition of the term and a new metric for it's measurement David Craven
2017-02-03 17:40 ` Taylan Ulrich Bayırlı/Kammer
2017-02-03 18:18   ` David Craven
2017-02-03 18:44     ` Christopher Howard
2017-02-03 20:12       ` David Craven
2017-02-05 22:53       ` [GNU-linux-libre] " Maxim Cournoyer
2017-02-10 17:31         ` David Craven
2017-02-10 18:21           ` Christopher Howard
2017-02-13  7:02             ` Maxim Cournoyer
2017-02-13  8:42               ` [GNU-linux-libre] " John Darrington
2017-02-13 19:24                 ` David Craven
2017-02-13 21:21                   ` [GNU-linux-libre] " Hartmut Goebel
2017-02-13 22:48                     ` David Craven
2017-02-14  6:55                   ` Maxim Cournoyer
2017-02-14 10:41                     ` [GNU-linux-libre] " David Craven
2017-02-14 17:47                       ` Maxim Cournoyer
2017-02-14 12:15 ` Denis 'GNUtoo' Carikli
2017-02-14 18:43   ` David Craven [this message]
2017-02-14 20:11     ` Adonay Felipe Nogueira
2017-02-14 20:47       ` David Craven
2017-02-14 20:57         ` Christopher Howard
2017-02-14 21:01           ` David Craven
2017-02-14 21:13             ` [GNU-linux-libre] " David Craven
2017-02-20  7:50     ` Denis 'GNUtoo' Carikli
2017-02-21 12:15       ` David Craven

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=CAL1_imnD_xpiWrWQvXgD_Qp2qLV3aNZ8W+xdk0F8tXabBVeoQw@mail.gmail.com \
    --to=david@craven.ch \
    --cc=GNUtoo@no-log.org \
    --cc=gnu-linux-libre@nongnu.org \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).