a5488b8be3f359feb05583c4e63b7ce49df9da
1 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] 2 helo=mx.sourceforge.net) 3 by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) 4 (envelope-from <gmaxwell@gmail.com>) id 1Vxzg6-00015a-7c 5 for bitcoin-development@lists.sourceforge.net; 6 Tue, 31 Dec 2013 13:48:14 +0000 7 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com 8 designates 209.85.217.182 as permitted sender) 9 client-ip=209.85.217.182; envelope-from=gmaxwell@gmail.com; 10 helo=mail-lb0-f182.google.com; 11 Received: from mail-lb0-f182.google.com ([209.85.217.182]) 12 by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) 13 (Exim 4.76) id 1Vxzg5-0001xK-Ap 14 for bitcoin-development@lists.sourceforge.net; 15 Tue, 31 Dec 2013 13:48:14 +0000 16 Received: by mail-lb0-f182.google.com with SMTP id l4so6105533lbv.41 17 for <bitcoin-development@lists.sourceforge.net>; 18 Tue, 31 Dec 2013 05:48:06 -0800 (PST) 19 MIME-Version: 1.0 20 X-Received: by 10.152.29.202 with SMTP id m10mr29703655lah.23.1388497686551; 21 Tue, 31 Dec 2013 05:48:06 -0800 (PST) 22 Received: by 10.112.198.65 with HTTP; Tue, 31 Dec 2013 05:48:06 -0800 (PST) 23 In-Reply-To: <CANAnSg3nPhrk2k=yDKf39AuBQnSuTWJbgANdMhGe=soiOy0NTw@mail.gmail.com> 24 References: <52A3C8A5.7010606@gmail.com> 25 <1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net> 26 <52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org> 27 <CANAnSg2OrmQAcZ+cZdtQeADicH3U29QOgYPfP1AQhOMP6+P1wg@mail.gmail.com> 28 <CAAS2fgR0khyJxmz9c2Oc87hOFgiNuiPJuaeugGajdo_EcKEW9w@mail.gmail.com> 29 <20131212205106.GA4572@netbook.cypherspace.org> 30 <CANAnSg3nPhrk2k=yDKf39AuBQnSuTWJbgANdMhGe=soiOy0NTw@mail.gmail.com> 31 Date: Tue, 31 Dec 2013 05:48:06 -0800 32 Message-ID: <CAAS2fgTmWRMxYweu3sNn_X7grgjUqTQujM-DbZRxG_YMZnD=7g@mail.gmail.com> 33 From: Gregory Maxwell <gmaxwell@gmail.com> 34 To: Drak <drak@zikula.org> 35 Content-Type: text/plain; charset=UTF-8 36 Content-Transfer-Encoding: quoted-printable 37 X-Spam-Score: -1.6 (-) 38 X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. 39 See http://spamassassin.org/tag/ for more details. 40 -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for 41 sender-domain 42 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider 43 (gmaxwell[at]gmail.com) 44 -0.0 SPF_PASS SPF: sender matches SPF record 45 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. 46 See 47 http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block 48 for more information. [URIs: zikula.org] 49 -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from 50 author's domain 51 0.1 DKIM_SIGNED Message has a DKIM or DK signature, 52 not necessarily valid 53 -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 54 X-Headers-End: 1Vxzg5-0001xK-Ap 55 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> 56 Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org, 57 your thoughts? 58 X-BeenThere: bitcoin-development@lists.sourceforge.net 59 X-Mailman-Version: 2.1.9 60 Precedence: list 61 List-Id: <bitcoin-development.lists.sourceforge.net> 62 List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 63 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> 64 List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> 65 List-Post: <mailto:bitcoin-development@lists.sourceforge.net> 66 List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> 67 List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 68 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> 69 X-List-Received-Date: Tue, 31 Dec 2013 13:48:14 -0000 70 71 On Tue, Dec 31, 2013 at 5:39 AM, Drak <drak@zikula.org> wrote: 72 > The NSA has the ability, right now to change every download of bitcoin-qt= 73 , 74 > on the fly and the only cure is encryption. 75 76 Please cut it out with the snake oil pedaling. This is really over the 77 top. You're invoking the NSA as the threat here? Okay. The NSA can 78 trivially compromise an HTTPS download site: even ignoring the CA 79 insecurity, and government run CAs certificate authorities issue CA 80 certs to random governments and corporations for dataloss prevention 81 purposes. Not to mention unparalleled access to exploits. 82 83 The downloads are protected by something far stronger than SSL 84 already, which might even have a chance against the NSA. Actual 85 signatures of the downloads with offline keys. 86 87 I'm all pro-SSL and all that, but you are=E2=80=94 piece by piece=E2=80=94 = 88 really 89 convincing me that it produces an entirely false sense of security 90 which is entirely unjustified. 91 92