From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Development priorities
Date: Thu, 16 Jun 2011 14:18:46 -0400 [thread overview]
Message-ID: <201106161418.48804.luke@dashjr.org> (raw)
In-Reply-To: <BANLkTimV+0mSqqmLYJeTdvxhM2PjtyXXMw@mail.gmail.com>
On Thursday, June 16, 2011 1:59:56 PM Jeff Garzik wrote:
> > 2) Wallet security.
>
> Agreed, though security professionals (and luke-jr) are already
> pointing out the wallet crypto mainly eliminates a bit of bad PR,
> rather than being a major crime deterrent.
>
> zooko on IRC had a pretty good suggestion: introduce a built-in
> facility for air-gapped wallets (multiple wallets), so that loss of
> your everyday transactional wallet does not mean loss of everything.
Even if you do this, a cracker can still simply send your encrypted wallet to
himself, secure-delete your local one, kill your client, and demand you
publish your password if you want some portion of your coins back.
I'm not sure there's *any* defense for an insecure PC. Maybe Bitcoin will end
up forcing people to reconsider their priorities when it comes to security...
next prev parent reply other threads:[~2011-06-16 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 16:32 Gavin Andresen
2011-06-16 17:12 ` Luke-Jr
2011-06-16 17:59 ` Jeff Garzik
2011-06-16 18:18 ` Luke-Jr [this message]
2011-06-16 18:24 ` phantomcircuit
2011-06-17 3:05 ` bgroff
2011-06-19 14:26 ` 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=201106161418.48804.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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