[seL4] US Army SBIR calls for open HW/SW stack

Steven Schear schear.steve at gmail.com
Tue Nov 26 02:58:20 PST 2019


The real tests are whether the openness includes the hardware's boot code.
This is often a very sticky issue as discovered flaws in the already
delivered HW or boot firmware can expose the manufacturer to law suits
regarding delivery of faulty products.

On Tue, Nov 26, 2019, 6:45 AM grarpamp <grarpamp at gmail.com> wrote:

> > https://www.sbir.gov/sbirsearch/detail/1508741
>
> >   OBJECTIVE: Current commodity computer hardware and software are
> >   proprietary. A thorough security review cannot be performed on
> >   systems with undisclosed components. Offeror shall research high
> >   assurance computer security based on a completely open hardware and
> >   software platform following Saltzer and Schroeder’s open design
> >   principles from 1975.
>
> https://en.wikipedia.org/wiki/Evaluation_Assurance_Level
> http://web.mit.edu/Saltzer/www/publications/protection/
> https://www.cs.virginia.edu/~evans/cs551/saltzer/
>
> #OpenFabs , #OpenHW , #OpenSW , #OpenAudit
>
> Now who said there was no demand for that
> and that it would be an unprofitable venture.
> You should have been working on it to get
> the drop on first dibs in the market... now
> you've got to compete with the $Big guys.
>
> You can still go for EAL7 and EAL8+ :)
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/html
Size: 2040 bytes
Desc: not available
URL: <https://lists.cpunks.org/pipermail/cypherpunks/attachments/20191126/62f2c5e3/attachment.txt>


More information about the cypherpunks mailing list