From: Wendell <w@grabhive•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Safe auto-updating
Date: Mon, 5 Aug 2013 16:39:49 +0200 [thread overview]
Message-ID: <EE3869FD-6D83-469A-BF4F-31B79CA9950F@grabhive.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
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
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next reply other threads:[~2013-08-05 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 14:39 Wendell [this message]
2013-08-05 15:54 ` Daniel F
2013-08-05 16:47 ` Alan Reiner
2013-08-05 17:14 ` Jim
2013-08-05 17:49 ` Peter Todd
2013-08-07 4:32 ` Wendell
2013-08-07 8:41 ` Mike Hearn
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=EE3869FD-6D83-469A-BF4F-31B79CA9950F@grabhive.com \
--to=w@grabhive$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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