From: Bastiaan van den Berg <buzz@spacedout.nl>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Fwd: Wallet Lock, Unlock BIP idea
Date: Thu, 14 Jan 2016 09:38:29 +0100 [thread overview]
Message-ID: <CACLj26+DkRkUT2B4=jscs2YWTx6iq+zOS2o33AOLnvuhznFdvw@mail.gmail.com> (raw)
In-Reply-To: <CANEdHmgBkwLxJNqEwoWCVL7Vrsiv8WZReJp2so+UvMG1A38Gmg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
You might not be aware, but the wallet supports encrypting. Which then
means that when Mr Badguy steals your wallet.dat, he cannot do anything
with it without the passphrase. See RPC calls 'encryptwallet'
'walletpassphrase' and 'walletlock'.
Also i'd like to say, that adding a big waving flag in the blockchain to
say you are locking/unlocking your wallet might not match good privacy
ethics ;)
--
buZz
[-- Attachment #2: Type: text/html, Size: 502 bytes --]
next prev parent reply other threads:[~2016-01-14 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANEdHmjczpys1RMaZAahE-L==xMDzuVT=eyVApCxU_AHswtEYQ@mail.gmail.com>
2016-01-13 23:47 ` [bitcoin-dev] Fwd: Wallet Lock, Unlock BIP idea Scott Morgan
2016-01-14 8:38 ` Bastiaan van den Berg [this message]
2016-01-14 18:26 Scott Morgan
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='CACLj26+DkRkUT2B4=jscs2YWTx6iq+zOS2o33AOLnvuhznFdvw@mail.gmail.com' \
--to=buzz@spacedout.nl \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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