public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Scott Morgan <scott@adligo.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Fwd: Wallet Lock, Unlock BIP idea
Date: Thu, 14 Jan 2016 12:26:57 -0600	[thread overview]
Message-ID: <CANEdHmhM+j=xrK8Lv+5hmVTC6VojGTF0dCiKDxcjYY51S4zPkg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

Hi Again (buZz),

   I am aware of wallet encryption, even if encryptwallet was NOT there you
could always copy wallet.dat and use a third party encryption /decryption
tool.   Also any encryption can be broken, although this may not be
profitable.   I know a few people who still have problems with intruders
taking copper pipe out of buildings in Chicago, which is also unprofitable
since commodity prices have crashed.
   Your right that a big waving flag in the block chain may be a bad idea,
I figured there would be a good way to obsfucate the information through
some one way encryption.  Then anyone could check if wallet '1ABC...' is
locked by encrypting the wallet address and comparing it to a list of
encrypted wallet addresses, but couldn't easily obtain a list of locked or
unlocking wallets.   I haven't done any detailed work on implementation
though, as I mentioned.

Cheers,
Scott

[-- Attachment #2: Type: text/html, Size: 1061 bytes --]

             reply	other threads:[~2016-01-14 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 18:26 Scott Morgan [this message]
     [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

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='CANEdHmhM+j=xrK8Lv+5hmVTC6VojGTF0dCiKDxcjYY51S4zPkg@mail.gmail.com' \
    --to=scott@adligo.com \
    --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