From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
Date: Tue, 9 Jun 2020 12:01:35 -0700
Message-ID: <694F4F62-00C1-4EA6-B379-F8DF019AA845@getmailspring.com> (raw)
In-Reply-To: <CAPweEDyws116d9oKzSPhx6MpH-8C-ncfd+uPH6D6hgVG7+63Cg@mail.gmail.com>
On Jun 9 2020, at 3:34 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 0:49 - billions of cryptocurrency is lost if the hardware wallet
> cryptochip cannot be trusted.
>
> that's the "fear" version. do we want to present a "fear" strategy?
> (you know what i mean)
>
> rework:
>
> 0:49 - cryptocurrency hardware wallets and banking identification
> terminals containing cryptochips can be trusted if the hardware is
> formally verified and the entire HDL available for a full independent
> audit.
Thanks, I like that formulation much better. I'll make these edits on
the wiki page, and send a link with the updated video later today. Or
Yehowshua may be able to embed the presentation. We will see.
Cole
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 23:42 Cole Poirier
2020-06-07 23:55 ` Luke Kenneth Casson Leighton
2020-06-08 0:29 ` Jacob Lifshay
2020-06-08 10:17 ` Staf Verhaegen
2020-06-08 11:13 ` Luke Kenneth Casson Leighton
2020-06-08 12:37 ` Staf Verhaegen
2020-06-08 13:55 ` Hendrik Boom
2020-06-08 14:15 ` Lauri Kasanen
2020-06-08 15:27 ` Luke Kenneth Casson Leighton
2020-06-09 1:17 ` Cole Poirier
2020-06-09 10:34 ` Luke Kenneth Casson Leighton
2020-06-09 19:01 ` Cole Poirier [this message]
2020-06-09 22:01 ` Hendrik Boom
2020-06-10 0:43 ` Cole Poirier
2020-06-10 0:44 ` Yehowshua
2020-06-10 2:46 ` Hendrik Boom
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=694F4F62-00C1-4EA6-B379-F8DF019AA845@getmailspring.com \
--to=colepoirier@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git