From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1V6N6v-0001R9-AK for bitcoin-development@lists.sourceforge.net; Mon, 05 Aug 2013 15:54:17 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.51 as permitted sender) client-ip=209.85.213.51; envelope-from=nanotube@gmail.com; helo=mail-yh0-f51.google.com; Received: from mail-yh0-f51.google.com ([209.85.213.51]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V6N6s-0004QT-0J for bitcoin-development@lists.sourceforge.net; Mon, 05 Aug 2013 15:54:17 +0000 Received: by mail-yh0-f51.google.com with SMTP id 29so1552305yhl.10 for ; Mon, 05 Aug 2013 08:54:08 -0700 (PDT) X-Received: by 10.236.192.225 with SMTP id i61mr11584677yhn.13.1375718048651; Mon, 05 Aug 2013 08:54:08 -0700 (PDT) Received: from [192.168.2.101] (c-68-81-47-73.hsd1.pa.comcast.net. [68.81.47.73]) by mx.google.com with ESMTPSA id l67sm37324359yhc.26.2013.08.05.08.54.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 08:54:07 -0700 (PDT) Message-ID: <51FFCA9A.6010208@gmail.com> Date: Mon, 05 Aug 2013 11:54:02 -0400 From: Daniel F User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 (nanotube[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: 1V6N6s-0004QT-0J Subject: Re: [Bitcoin-development] Safe auto-updating X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 15:54:17 -0000 If you want package authentication, you should at least throw in some digital signing, not just a checksum. With a compromised host, both the checksum and binaries can be changed undetectably, but if there's a signature made by a key that is not kept on the host, there's no way to fake a valid binary. There may be other issues people would want to bring up, but surely just a checksum is not sufficient. on 08/05/2013 10:39 AM Wendell said the following: > For usability purposes, we at Hive would like to have an > auto-updater in our wallet app. > > What is a safe way to do this? I understand that Bitcoin-QT lacks > such an updater for security reasons... Has been thought out in more detail since that decision was made? > > We have been toying around with the idea of placing one server > behind a Tor hidden service, whose only function is to output a checksum of the update package. The theory is that if it is well-secured, it will at least be immune to tampering at the physical hosting level. > > Any thoughts or advice about any of this? > -wendell > > grabhive.com | twitter.com/grabhive | gpg: 6C0C9411 > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >