diff options
| author | Thy Shizzle <thyshizzle@outlook.com> | 2015-03-23 14:38:20 +1100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2015-03-23 03:38:38 +0000 |
| commit | 9bccb56c280fb4242c78b33b546dc51f38992a6c (patch) | |
| tree | 857882e612a7ad95953f28accb23c587ad23d46f | |
| parent | ae06d94934f12809350e3a1a9352cc1c090e417d (diff) | |
| download | pi-bitcoindev-9bccb56c280fb4242c78b33b546dc51f38992a6c.tar.gz pi-bitcoindev-9bccb56c280fb4242c78b33b546dc51f38992a6c.zip | |
Re: [Bitcoin-development] Criminal complaints against "network disruption as a service" startups
| -rw-r--r-- | 1d/23f1c4c887ca3208fc5c446863b4b7560bdbd0 | 243 |
1 files changed, 243 insertions, 0 deletions
diff --git a/1d/23f1c4c887ca3208fc5c446863b4b7560bdbd0 b/1d/23f1c4c887ca3208fc5c446863b4b7560bdbd0 new file mode 100644 index 000000000..0be9e8b81 --- /dev/null +++ b/1d/23f1c4c887ca3208fc5c446863b4b7560bdbd0 @@ -0,0 +1,243 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <thyshizzle@outlook.com>) id 1YZtCI-0002qZ-1J + for bitcoin-development@lists.sourceforge.net; + Mon, 23 Mar 2015 03:38:38 +0000 +Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of outlook.com + designates 65.55.34.203 as permitted sender) + client-ip=65.55.34.203; envelope-from=thyshizzle@outlook.com; + helo=COL004-OMC4S1.hotmail.com; +Received: from col004-omc4s1.hotmail.com ([65.55.34.203]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) + (Exim 4.76) id 1YZtCF-0006Tg-SD + for bitcoin-development@lists.sourceforge.net; + Mon, 23 Mar 2015 03:38:38 +0000 +Received: from COL401-EAS227 ([65.55.34.200]) by COL004-OMC4S1.hotmail.com + over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); + Sun, 22 Mar 2015 20:38:29 -0700 +X-TMN: [46DgPxs5eaJUUGHe0qD7zuBg+6+AccWX] +X-Originating-Email: [thyshizzle@outlook.com] +Message-ID: <COL401-EAS2273FA9CFE9B779BF339766C20D0@phx.gbl> +MIME-Version: 1.0 +To: odinn <odinn.cyberguerrilla@riseup.net> +From: Thy Shizzle <thyshizzle@outlook.com> +Date: Mon, 23 Mar 2015 14:38:20 +1100 +Content-Transfer-Encoding: quoted-printable +Content-Type: text/plain; charset="utf-8" +X-OriginalArrivalTime: 23 Mar 2015 03:38:29.0828 (UTC) + FILETIME=[D4404040:01D0651A] +X-Spam-Score: -1.5 (-) +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 + (thyshizzle[at]outlook.com) + -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, + no trust [65.55.34.203 listed in list.dnswl.org] + -0.0 SPF_PASS SPF: sender matches SPF record +X-Headers-End: 1YZtCF-0006Tg-SD +Cc: bitcoin-development@lists.sourceforge.net +Subject: Re: [Bitcoin-development] Criminal complaints against "network + disruption as a service" startups +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: Mon, 23 Mar 2015 03:38:38 -0000 + +I don't believe that at all. Analyzing information publicly available is no= +t illegal. Chainalysis or whatever you call it would be likened to observin= +g who comes and feeds birds at the park everyday. You can sit in the park a= +nd observe who feeds the birds, just as you can connect to the Bitcoin P2P = +network and observe the blocks being formed into the chain and transactions= + etc. Unless there is some agreement taking place where it is specified tha= +t upon connecting to the Bitcoin P2P swarm you agree to a set of terms, how= +ever as every node is providing their own "entry" into the P2P swarm it bec= +omes really up to the node providing the connection to uphold and enforce t= +he terms of the agreement. If you allow people to connect to you without te= +rms of agreement, you cannot cry foul when they record the data that passes= + through. To say Chainalysis needs to cease is silly, the whole point of th= +e public blockchain is for Chainalysis, whether it be for the verification = +of transactions, research or otherwise. + +-----Original Message----- +From: "odinn" <odinn.cyberguerrilla@riseup.net> +Sent: =E2=80=8E23/=E2=80=8E03/=E2=80=8E2015 1:48 PM +To: "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.= +sourceforge.net> +Subject: Re: [Bitcoin-development] Criminal complaints against "network dis= +ruption as a service" startups + +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +If you (e.g. Chainalysis) or anyone else are doing surveillance on the +network and gathering information for later use, and whether or not +the ultimate purpose is to divulge it to other parties for compliance +purposes, you can bet that ultimately the tables will be turned on +you, and you will be the one having your ass handed to you so to +speak, before or after you are served, in legal parlance. Whether or +not the outcome of that is meaningful and beneficial to any concerned +parties and what is the upshot of it in the end depends on on what you +do and just how far you decide to take your ill-advised enterprise. + +Chainalysis and similar operations would be, IMHO, well advised to +cease operations. This doesn't mean they will, but guess what: + +Shot over the bow, folks. + +Jan M=C3=B8ller: +> What we were trying to achieve was determining the flow of funds +> between countries by figuring out which country a transaction +> originates from. To do that with a certain accuracy you need many +> nodes. We chose a class C IP range as we knew that bitcoin core and +> others only connect to one node in any class C IP range. We were +> not aware that breadwallet didn't follow this practice. Breadwallet +> risked getting tar-pitted, but that was not our intention and we +> are sorry about that. +>=20 +> Our nodes DID respond with valid blocks and merkle-blocks and +> allowed everyone connecting to track the blockchain. We did however +> not relay transactions. The 'service' bit in the version message is +> not meant for telling whether or how the node relays transactions, +> it tells whether you can ask for block headers only or full +> blocks. +>=20 +> Many implementations enforce non standard rules for handling +> transactions; some nodes ignore transactions with address reuse, +> some nodes happily forward double spends, and some nodes forward +> neither blocks not transactions. We did blocks but not +> transactions. +>=20 +> In hindsight we should have done two things: 1. relay transactions=20 +> 2. advertise address from 'foreign' nodes +>=20 +> Both would have fixed the problems that breadwallet experienced. +> My understanding is that breadwallet now has the same 'class C' +> rule as bitcoind, which would also fix it. +>=20 +> Getting back on the topic of this thread and whether it is illegal, +> your guess is as good as mine. I don't think it is illegal to log +> incoming connections and make statistical analysis on it. That +> would more or less incriminate anyone who runs a web-server and +> looks into the access log. At lease one Bitcoin service has been +> collecting IP addresses for years and given them to anyone visiting +> their web-site (you know who) and I believe that this practise is +> very wrong. We have no intention of giving IP addresses away to +> anyone, but we believe that you are free to make statistics on +> connection logs when nodes connect to you. +>=20 +> On a side note: When you make many connections to the network you +> see lots of strange nodes and suspicious patterns. You can be +> certain that we were not the only ones connected to many nodes. +>=20 +> My takeaway from this: If nodes that do not relay transactions is a +> problem then there is stuff to fix. +>=20 +> /Jan +>=20 +> On Fri, Mar 13, 2015 at 10:48 PM, Mike Hearn <mike@plan99.net> +> wrote: +>=20 +>> That would be rather new and tricky legal territory. +>>=20 +>> But even putting the legal issues to one side, there are +>> definitional issues. +>>=20 +>> For instance if the Chainalysis nodes started following the +>> protocol specs better and became just regular nodes that happen +>> to keep logs, would that still be a violation? If so, what about +>> blockchain.info? It'd be shooting ourselves in the foot to try +>> and forbid block explorers given how useful they are. +>>=20 +>> If someone non-maliciously runs some nodes with debug logging +>> turned on, and makes full system backups every night, and keeps +>> those backups for years, are they in violation of whatever +>> pseudo-law is involved? +>>=20 +>> I think it's a bit early to think about these things right now. +>> Michael Gr=C3=B8nager and Jan M=C3=B8ller have been Bitcoin hackers for = +a +>> long time. I'd be interested to know their thoughts on all of +>> this. +>>=20 +>>=20 +>> ------------------------------------------------------------------------= +------ +>> +>>=20 +Dive into the World of Parallel Programming The Go Parallel Website, +>> sponsored by Intel and developed in partnership with Slashdot +>> Media, is your hub for all things parallel software development, +>> from weekly thought leadership blogs to news, videos, case +>> studies, tutorials and more. Take a look and join the=20 +>> conversation now. http://goparallel.sourceforge.net/=20 +>> _______________________________________________=20 +>> Bitcoin-development mailing list=20 +>> Bitcoin-development@lists.sourceforge.net=20 +>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development +>>=20 +>>=20 +>=20 +>=20 +>=20 +> -------------------------------------------------------------------------= +----- +> +>=20 +Dive into the World of Parallel Programming The Go Parallel Website, +sponsored +> by Intel and developed in partnership with Slashdot Media, is your +> hub for all things parallel software development, from weekly +> thought leadership blogs to news, videos, case studies, tutorials +> and more. Take a look and join the conversation now. +> http://goparallel.sourceforge.net/ +>=20 +>=20 +>=20 +> _______________________________________________ Bitcoin-development +> mailing list Bitcoin-development@lists.sourceforge.net=20 +> https://lists.sourceforge.net/lists/listinfo/bitcoin-development +>=20 + +- --=20 +http://abis.io ~ +"a protocol concept to enable decentralization +and expansion of a giving economy, and a new social good" +https://keybase.io/odinn +-----BEGIN PGP SIGNATURE----- + +iQEcBAEBCgAGBQJVD34mAAoJEGxwq/inSG8CvrQH/28Rt26oGdo9rS+PaR1fIQ1p +Jwks11Axsmu5x3emTgIz0xUJ6zz/4ERM0LeNLBpfSFwZyLbuCgw1uiJplT+9uPgY +hPXb9OTNejfWZJjYc3i6rNjf2SNc5E3/4PtgeOI6lI/SsGQ6ineNm6gFjwe8xVpt +wCLOPetzCukQegXluFZZdALnPDf4H9yAeSsrfX2h2iCBAJ3qd9f1DP7+e6hvr+xr +POVBjlRYtnSd/viKJ2IhMbRvnqd86pRNAKEWrjZp0CIkGyY7wh4nqtYErZi4TcOK +H7yhU8o4/mgTNSIYdLTOSMlRi+nTMPWUD2jvO/Z9i9VTR9afn8E7j7iHD6QPMB0=3D +=3DvdbG +-----END PGP SIGNATURE----- + +---------------------------------------------------------------------------= +--- +Dive into the World of Parallel Programming The Go Parallel Website, sponso= +red +by Intel and developed in partnership with Slashdot Media, is your hub for = +all +things parallel software development, from weekly thought leadership blogs = +to +news, videos, case studies, tutorials and more. Take a look and join the=20 +conversation now. http://goparallel.sourceforge.net/ +_______________________________________________ +Bitcoin-development mailing list +Bitcoin-development@lists.sourceforge.net +https://lists.sourceforge.net/lists/listinfo/bitcoin-development= + + |