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
74
75
76
77
78
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1UPeAr-0000Ad-AW
for bitcoin-development@lists.sourceforge.net;
Tue, 09 Apr 2013 19:25:45 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.181 as permitted sender)
client-ip=209.85.217.181; envelope-from=gmaxwell@gmail.com;
helo=mail-lb0-f181.google.com;
Received: from mail-lb0-f181.google.com ([209.85.217.181])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UPeAq-00021q-H3
for bitcoin-development@lists.sourceforge.net;
Tue, 09 Apr 2013 19:25:45 +0000
Received: by mail-lb0-f181.google.com with SMTP id r11so7171371lbv.40
for <bitcoin-development@lists.sourceforge.net>;
Tue, 09 Apr 2013 12:25:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.87.73 with SMTP id v9mr14834277laz.2.1365535537714; Tue,
09 Apr 2013 12:25:37 -0700 (PDT)
Received: by 10.112.134.164 with HTTP; Tue, 9 Apr 2013 12:25:37 -0700 (PDT)
In-Reply-To: <51642835.1040007@lavabit.com>
References: <CA+8xBpc5iV=prakWKkNFa0O+tgyhoHxJ9Xwz6ubhPRUBf_95KA@mail.gmail.com>
<CANEZrP1EKaHbpdC6X=9mvyJHC_cvW7u5p9nqM7EwkEypAg4Xmg@mail.gmail.com>
<51642835.1040007@lavabit.com>
Date: Tue, 9 Apr 2013 12:25:37 -0700
Message-ID: <CAAS2fgSLQ9yQrt7SZ0xRp7rZ22SA7+nDKtP3fSxU3tYgd_=30A@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Caleb James DeLisle <calebdelisle@lavabit.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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: 1UPeAq-00021q-H3
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] On-going data spam
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: Tue, 09 Apr 2013 19:25:45 -0000
On Tue, Apr 9, 2013 at 7:39 AM, Caleb James DeLisle
<calebdelisle@lavabit.com> wrote:
> what anti-virus software might do when certain streams of bytes are sent =
across
> the tcp socket or persisted to disk. Perhaps worth contacting an AV compa=
ny and
> asking what is the smallest data they have a signature on.
I stuffed the testnet chain full of the EICAR test string and it
hasn't triggered for anyone=E2=80=94 it seems that (most?) AV tools do not
scan big binary files of unknown type.. apparently.
If we encounter a case where they do we can implement storage
scrambling: E.g. every node picks a random word and all their stored
data is xored with it.
|
