From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giovanni Biscuolo Subject: Re: GuixSD on librem phone? Date: Thu, 06 Dec 2018 16:24:38 +0100 Message-ID: <87d0qek79l.fsf@roquette.mug.biscuolo.net> References: <87ftvahip5.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me> <87d0qehhrl.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUvWb-0006Gx-Jq for guix-devel@gnu.org; Thu, 06 Dec 2018 10:25:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gUvWX-0004l6-7G for guix-devel@gnu.org; Thu, 06 Dec 2018 10:25:13 -0500 Received: from ns13.heimat.it ([46.4.214.66]:40146) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUvWW-0004iC-Ra for guix-devel@gnu.org; Thu, 06 Dec 2018 10:25:09 -0500 In-Reply-To: <87d0qehhrl.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Vagrant Cascadian , guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi! sorry for going little bit OT I'm *desperately* looking forward for hardware I can trust, so librem5 is giving me *some* hope, but... Vagrant Cascadian writes: [...] > https://puri.sm/posts/librem5-2018-09-hardware-report/ > > Apparently they will use wifi/bluetooth/cellular that has proprietary > firmware, but burned into the hardware, which is compliant with the RYF > guidelines... still in 2018 the hardware landscape is so sad that a quite "freedom committed" vendor [1] cannot find a better alternative than to use a proprietary wifi and bluetooth stack: OK, RFY compliant but what _when_ (not if) a serious bug will be found on that firmware? are we sure wifi/bluetooth cannot be used as "side channel" vector attacks? 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) 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] :-) [...] Ciao Giovanni [1] citing from the above mentioned article: =C2=ABThis is highlighting the fact that Purism, as a social purpose corporation, will push our strict agenda of software and user freedoms upstream into the supply chain.=C2=BB [2] looking at you, secushare https://secushare.org/ =2D-=20 Giovanni Biscuolo Xelera IT Infrastructures --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAlwJPzYACgkQ030Op87M ORI3ZhAAnOTVKboEzRUx+nDzM46JOs3BKmao96zplB6rsWTqyPGIKnNuTYIoqk/y RY8rQgpcwnVcZZ60dtb4IvzCuEPQDd1IrcaPDu+u4x2HxYrR1DovxoiXFV90zlWt ShdYTCq8YWaJcyol7fQ/CmeOfebgHffdvt2BD7R9nTFKvMxo7GRV7zNDVUw7musi NGbKWHo3IQ1wHMT5JVMSbF8WquoI5DwlfUxu4UtfPhugFvTwF2zVpYasfxhHCtlO qjpAxEOOwE2JlnrQa7FVH8jN4W7WtuqMneMkQQGuEvyl5tiTHo9sTUj2qSDZxEk0 gMj+VC1bdlMXKAysqNrUdP0nw6oVoTDoCxoDvnhx/Y2RNSjfb/O3q7e7Huj62UTF 8P/CL6PfA+BK6SoT1U0XnXAEeuLAfeygZBrmAiDodDqia2A+zXAMmrQtueJKsPNd xIGRaJN9YKjeoPF3cTDlasmj/9j3Fk7QjNTbRREq56vAaW9BrurChhGbfWfNUANw Ea4naXQpCKB50prZXx2bHl5QTw73NfoyA/EnOFtBzBbcf5RpUyYxwerFp06SyQKi CMEI4NmXopgaijaSiW06r8UgeyZVjC69MWBQ1WxFQUmmiJEu8JjHSKOmIgli/rvt HD7CM3EoL1fR9U5UacwK5oQJNFEcAyX2mZi4FssZr9YmpL9tUgw= =HbkD -----END PGP SIGNATURE----- --=-=-=--