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 <jayschwa@gmail.com>) id 1TZNNW-0005vi-Gi for bitcoin-development@lists.sourceforge.net; Fri, 16 Nov 2012 14:58:46 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.175 as permitted sender) client-ip=209.85.223.175; envelope-from=jayschwa@gmail.com; helo=mail-ie0-f175.google.com; Received: from mail-ie0-f175.google.com ([209.85.223.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TZNNV-0005yA-S0 for bitcoin-development@lists.sourceforge.net; Fri, 16 Nov 2012 14:58:46 +0000 Received: by mail-ie0-f175.google.com with SMTP id c13so3837522ieb.34 for <bitcoin-development@lists.sourceforge.net>; Fri, 16 Nov 2012 06:58:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.161.130 with SMTP id xs2mr3422741igb.34.1353077920643; Fri, 16 Nov 2012 06:58:40 -0800 (PST) Received: by 10.64.12.69 with HTTP; Fri, 16 Nov 2012 06:58:40 -0800 (PST) Date: Fri, 16 Nov 2012 08:58:40 -0600 Message-ID: <CANAndtxJj2n+SfN9vpL61DPnNfNvNWEa+8mk6diUmc=S89e=Gw@mail.gmail.com> From: Jay Weisskopf <jayschwa@gmail.com> To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1 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 (jayschwa[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: 1TZNNV-0005yA-S0 Subject: [Bitcoin-development] TLS (SSL) for bitcoin.org and downloads 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, 16 Nov 2012 14:58:46 -0000 Are there any plans to eventually force TLS (SSL) for bitcoin.org and its downloads? - Jay