[Freedombox-discuss] why choose new OSHW (Open Source HardWare)

[Jack Wilborn]

Roy and Bibbet have valid points.  While searching for hardware for
vaporware is not a good idea, the fact that we can build a system that will
load and run any Debian flavor seems to be the best direction.  Once we
have a working model we can then say, it needs hardware encrypt/decrypt or
whatever.  It needs to be able to run code in a protected environment and
so forth.

My opinion, and hardware is my game, is to develop with what we currently
have, maybe if someone wants to include the RPi then let them it can not
hurt us and will allow testing on a wider variety of machine.  Until the
system is virtually complete, chasing hardware is expensive.  Hopefully
some manufacturer will look at us and request 'desirable' properties for a
machine.

For now, lets build for what we are using, adding platforms when we can.
The more the merrier?  Of course I own a Dreamplug, but I have other places
that I could use it.  Lets build a portable system, if practical.  I say if
practical because I know how much hardware differs and the more platforms
the tougher it is to locate and step on bug (let's hope none come to their
funerals).

IMHO

Jack


On Wed, Jul 3, 2013 at 6:43 AM, Blibbet <blibbet at gmail.com> wrote:

> Opinions are quite welcome.
>>
>
> While it is early to pick hardware for vapor, it would be useful to plan
> on the firmware requirements, not just the OS. UEFI, Coreboot, or something
> else (what?). As well as if box should have TPM or not, if Intel, and
> TrustZone or not, if ARM, for OEM hareware requiements, and potentially for
> OS security stack requirements.
>
> For example, I'd hope FreedomBox Foundation is looking for an OEM that'll
> build ARM-based boxes with TrustZone, using UEFI, which properly uses
> Secure Boot feature to load OS. And uses TPM/TrustZone to Securely Boot
> Linux-based FreedomBox, and to attest the software stack is still intact
> (like strongSwan's ipSec does).
>
> I don't know if Linux-IMA is ready for ARM TrustZone. So you might only
> have a solution for x86 boxes at the moment. But, it'll be years before FBF
> is talking to OEMs, so perhaps time to fix that. :-)
>
>
>
> ______________________________**_________________
> Freedombox-discuss mailing list
> Freedombox-discuss at lists.**alioth.debian.org<Freedombox-discuss at lists.alioth.debian.org>
> http://lists.alioth.debian.**org/cgi-bin/mailman/listinfo/**
> freedombox-discuss<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20130703/fbe91776/attachment.html>