1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1UxeNy-0001tZ-Pq
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Jul 2013 14:31:50 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.176 as permitted sender)
client-ip=209.85.217.176; envelope-from=gmaxwell@gmail.com;
helo=mail-lb0-f176.google.com;
Received: from mail-lb0-f176.google.com ([209.85.217.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UxeNy-0002Wx-2K
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Jul 2013 14:31:50 +0000
Received: by mail-lb0-f176.google.com with SMTP id z5so7570348lbh.21
for <bitcoin-development@lists.sourceforge.net>;
Fri, 12 Jul 2013 07:31:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.74.47 with SMTP id q15mr19538715lbv.75.1373639503357;
Fri, 12 Jul 2013 07:31:43 -0700 (PDT)
Received: by 10.112.160.104 with HTTP; Fri, 12 Jul 2013 07:31:43 -0700 (PDT)
In-Reply-To: <604065f299f2f3ef79747f969475042c.squirrel@webmail.xs4all.nl>
References: <604065f299f2f3ef79747f969475042c.squirrel@webmail.xs4all.nl>
Date: Fri, 12 Jul 2013 07:31:43 -0700
Message-ID: <CAAS2fgQe4wO5J=4r3Lc-JsXJrQmaUqnD59=5eKorbZ+EMuXT-A@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: capibara@xs4all.nl
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UxeNy-0002Wx-2K
Cc: Bitcoin-Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Review for slides for "defeating trojans"
talk
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 12 Jul 2013 14:31:51 -0000
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.
|
