From: Gregory Maxwell <gmaxwell@gmail•com>
To: capibara@xs4all•nl
Cc: Bitcoin-Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Review for slides for "defeating trojans" talk
Date: Fri, 12 Jul 2013 07:31:43 -0700 [thread overview]
Message-ID: <CAAS2fgQe4wO5J=4r3Lc-JsXJrQmaUqnD59=5eKorbZ+EMuXT-A@mail.gmail.com> (raw)
In-Reply-To: <604065f299f2f3ef79747f969475042c.squirrel@webmail.xs4all.nl>
On Fri, Jul 12, 2013 at 7:28 AM, Rob Meijer <rmeijer@xs4all•nl> wrote:
> Completed the first draft of my slides+speaker-notes for my upcoming
> "Defeating Trojans" talk at the OHM2013. BitCoin is one of the main
> examples I use in this talk to emphasize the need for programs like
> BitCoin to have
> their own private storage apart from $HOME.
>
> To make sure I don't misrepresent BitCoin, could anyone here help me out
> by reviewing my slides, please let me know and I'll e-mail my (open
> office) slides to you for review.
I'm game.
next prev parent reply other threads:[~2013-07-12 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 14:28 Rob Meijer
2013-07-12 14:31 ` Gregory Maxwell [this message]
2013-07-12 16:46 Mats Henricson
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='CAAS2fgQe4wO5J=4r3Lc-JsXJrQmaUqnD59=5eKorbZ+EMuXT-A@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=capibara@xs4all$(echo .)nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox