From: Gregory Maxwell <gmaxwell@gmail•com>
To: Caleb James DeLisle <calebdelisle@lavabit•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] On-going data spam
Date: Tue, 9 Apr 2013 12:25:37 -0700 [thread overview]
Message-ID: <CAAS2fgSLQ9yQrt7SZ0xRp7rZ22SA7+nDKtP3fSxU3tYgd_=30A@mail.gmail.com> (raw)
In-Reply-To: <51642835.1040007@lavabit.com>
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 company 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— 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.
next prev parent reply other threads:[~2013-04-09 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 1:22 Jeff Garzik
2013-04-09 9:28 ` Peter Todd
2013-04-09 10:42 ` Mike Hearn
2013-04-09 11:09 ` Peter Todd
2013-04-09 11:17 ` Jay F
2013-04-09 11:34 ` Robert Backhaus
2013-04-09 14:14 ` Mike Hearn
2013-04-09 14:39 ` Caleb James DeLisle
2013-04-09 18:56 ` steve
2013-04-09 19:25 ` Gregory Maxwell [this message]
2013-04-09 19:43 ` Mike Hearn
2013-04-09 14:50 ` Jeff Garzik
2013-04-09 14:53 ` Mike Hearn
2013-04-09 15:01 ` Jeff Garzik
2013-04-09 17:58 ` Peter Todd
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='CAAS2fgSLQ9yQrt7SZ0xRp7rZ22SA7+nDKtP3fSxU3tYgd_=30A@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=calebdelisle@lavabit$(echo .)com \
/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