all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: GuixSD on librem phone?
Date: Thu, 6 Dec 2018 16:13:51 -0500	[thread overview]
Message-ID: <20181206211351.GB909@jasmine.lan> (raw)
In-Reply-To: <87d0qek79l.fsf@roquette.mug.biscuolo.net>

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

On Thu, Dec 06, 2018 at 04:24:38PM +0100, Giovanni Biscuolo wrote:
> callular (baseband) merits a dedicated chapter, since it seems
> practically impossible *forever* to trust that chips... and that chips
> are an important attack vector (Purism will use USB bus to separate
> baseband from CPU)

I agree, the situation is depressing...

> this also means we will _never_ be able to trust communications via
> baseband (2G, 3G... 5G), fortunately this can be fixed using a trusted
> _separated_ SoC and the very good work coming from the vast and smart
> FLOSS community [2] :-)

... but we can trust communications over cellular baseband. Already, we
have built many trustable communication systems over untrusted mediums
like the internet. This is the role of things like TLS, the Signal
double-ratchet, and PGP.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-12-06 21:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 11:57 GuixSD on librem phone? swedebugia
2018-12-06 13:45 ` Vagrant Cascadian
2018-12-06 14:06   ` Vagrant Cascadian
2018-12-06 15:24     ` Giovanni Biscuolo
2018-12-06 21:13       ` Leo Famulari [this message]
2018-12-06 22:31         ` Giovanni Biscuolo
2018-12-06 13:55 ` Pierre Neidhardt
2018-12-06 17:03 ` Jan Nieuwenhuizen
2018-12-09 15:11 ` Divan Santana

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

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

  git send-email \
    --in-reply-to=20181206211351.GB909@jasmine.lan \
    --to=leo@famulari.name \
    --cc=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.