1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
Return-Path: <scott@adligo.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 60FA498D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Jan 2016 18:26:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f171.google.com (mail-io0-f171.google.com
[209.85.223.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C7BC179
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Jan 2016 18:26:57 +0000 (UTC)
Received: by mail-io0-f171.google.com with SMTP id q21so462014996iod.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 14 Jan 2016 10:26:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=adligo-com.20150623.gappssmtp.com; s=20150623;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=vrXhIlHkaaHGp8hs0TecQjBugQ59krQhu4Gnb04O4F4=;
b=YqYEIJe6HpOHWT/RH2g4rF6aNpAWa2hmZYRbo8CsYdhS8MUD8MYQCR90/icC7ejSmb
965ACio0vinp8S7yu2/k97NMvEGVLjrbBQGRXG4yIMSCr/BK4L3Cdd/Rn5609QLm5rXC
vvzup2YNFqG/DWjnkZwc9A6UydG5hRUbKdAM43Qcw37e3IGKC/9ijxIQPDRndhFNtxYq
2BnDU8ADpdmk82B+hnKycnpMX6zCSnIFoDFup0dwDBHhKhjVLaTwNuw25JvGjDqaooS9
DtidY8BxoHVkdl9FCBVJzExLMRkZnMoSkKDefzSM5i3VDB667m2r1i8XMAVWVvaXHwG3
AGoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:date:message-id:subject:from:to
:content-type;
bh=vrXhIlHkaaHGp8hs0TecQjBugQ59krQhu4Gnb04O4F4=;
b=eZCQd/TJbNlblYvGDRASpX4Ml9ilz2wLy9NndhRBmqX8TY02HEPt7AwyzViLeEPlLc
YzTYyzJ73tiluqhFmC12HDqJCF8XQIyPW6cCaxA2e6lxEMvaE4Y8Mfpl6h7I8YLDmzwz
rYtnJDxfP9H2/JReHGw47/CNaaQYNd2xL7Bxo9R6oKFZN46gbvVlz/kz8VShX5mgBeEg
KljkPhaD6flCXuAJ3FshFFPl4YwmqXHIdTCYwQw+7CWBQzC1geEfwAJUJqjy3BCTTbXa
GlwNzEcSl+K9ZHl7D1Vea6cwo3UrDdbZCFczXpVEoIWnOEEKDN9vjh7qjBp75RwLOqrx
J7mQ==
X-Gm-Message-State: ALoCoQkhroFP3sWwPV2iT9VL3uUl+8nNaAFd85pJfX9DpKMUZ8nCAXQ+5NYu/inpw2LOMOj+r5EiAJwnxTU4uNSL9ocR+HbuDw==
MIME-Version: 1.0
X-Received: by 10.107.157.205 with SMTP id g196mr5780894ioe.144.1452796017151;
Thu, 14 Jan 2016 10:26:57 -0800 (PST)
Received: by 10.64.35.19 with HTTP; Thu, 14 Jan 2016 10:26:57 -0800 (PST)
Date: Thu, 14 Jan 2016 12:26:57 -0600
Message-ID: <CANEdHmhM+j=xrK8Lv+5hmVTC6VojGTF0dCiKDxcjYY51S4zPkg@mail.gmail.com>
From: Scott Morgan <scott@adligo.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a1140a56288ac1405294f6e42
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 14 Jan 2016 20:08:43 +0000
Subject: Re: [bitcoin-dev] Fwd: Wallet Lock, Unlock BIP idea
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2016 18:26:58 -0000
--001a1140a56288ac1405294f6e42
Content-Type: text/plain; charset=UTF-8
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
--001a1140a56288ac1405294f6e42
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div>Hi Again (buZz),<br><br></div>=C2=A0=
=C2=A0 I am aware of wallet encryption, even if encryptwallet was NOT there=
you could always copy wallet.dat and use a third party encryption /decrypt=
ion tool.=C2=A0=C2=A0 Also any encryption can be broken, although this may =
not be profitable.=C2=A0=C2=A0 I know a few people who still have problems =
with intruders taking copper pipe out of buildings in Chicago, which is als=
o unprofitable since commodity prices have crashed.=C2=A0=C2=A0 <br></div>=
=C2=A0=C2=A0 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.=C2=A0 Then anyone could check if wallet &#=
39;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.=C2=A0=C2=A0 I haven't done any det=
ailed work on implementation though, as I mentioned.<br></div><div>=C2=A0 <=
br></div>Cheers,<br></div>Scott<br><div><div>=C2=A0 <br></div></div></div>
--001a1140a56288ac1405294f6e42--
|
