blob: 0256fd04dbaa00aa4be05b2c5ca08fff4af6c8e6 (
plain)
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
id 1YEEFL-0003Do-Rn for bitcoin-development@lists.sourceforge.net;
Thu, 22 Jan 2015 09:40:15 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of m.gmane.org
designates 80.91.229.3 as permitted sender)
client-ip=80.91.229.3;
envelope-from=gcbd-bitcoin-development@m.gmane.org;
helo=plane.gmane.org;
Received: from plane.gmane.org ([80.91.229.3])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1YEEFH-00056l-B8
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Jan 2015 09:40:15 +0000
Received: from list by plane.gmane.org with local (Exim 4.69)
(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
id 1YEEFA-0005bf-D3 for bitcoin-development@lists.sourceforge.net;
Thu, 22 Jan 2015 10:40:04 +0100
Received: from ip4d151d66.dynamic.kabel-deutschland.de ([77.21.29.102])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00 for <bitcoin-development@lists.sourceforge.net>;
Thu, 22 Jan 2015 10:40:04 +0100
Received: from for-gmane by ip4d151d66.dynamic.kabel-deutschland.de with local
(Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
for <bitcoin-development@lists.sourceforge.net>;
Thu, 22 Jan 2015 10:40:04 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: bitcoin-development@lists.sourceforge.net
From: "U.Mutlu" <for-gmane@mutluit.com>
Date: Thu, 22 Jan 2015 10:36:23 +0100
Organization: mutluit.com
Message-ID: <m9qgan$bk1$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: ip4d151d66.dynamic.kabel-deutschland.de
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64;
rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YEEFH-00056l-B8
Subject: [Bitcoin-development] Securing wallet on paper
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 09:40:16 -0000
I don't know yet the details of how a wallet looks like internally,
but I think it should be possible to print the wallet incl. acct nbr
out on classical paper (as base16 or base64 etc.) for filing it
in a physical home or bank safe.
Later, typing it from paper to a small converter program that recreates the
wallet file.
IMO this is a good security against possible computer hardware disasters.
Of course one has to secure this further with encryption against bank
fraud/theft etc.
Ie. the output on paper should be encrypted, and the owner
should place the key somewhere else.
I would suggest the developers make such functionality available for the user.
cu
Uenal
|
