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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1Wagv6-0002f0-VQ
for bitcoin-development@lists.sourceforge.net;
Thu, 17 Apr 2014 07:39:41 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.173 as permitted sender)
client-ip=209.85.223.173; envelope-from=laanwj@gmail.com;
helo=mail-ie0-f173.google.com;
Received: from mail-ie0-f173.google.com ([209.85.223.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wagv4-0002CB-Te
for bitcoin-development@lists.sourceforge.net;
Thu, 17 Apr 2014 07:39:40 +0000
Received: by mail-ie0-f173.google.com with SMTP id rl12so65757iec.18
for <bitcoin-development@lists.sourceforge.net>;
Thu, 17 Apr 2014 00:39:33 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.178.197 with SMTP id ox5mr8026284icc.22.1397720373592;
Thu, 17 Apr 2014 00:39:33 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Thu, 17 Apr 2014 00:39:33 -0700 (PDT)
In-Reply-To: <CAAS2fgRDmmv_EhUTRBfh8sBbCAoG_jcJeHE4fsKTHzOjoci4Gg@mail.gmail.com>
References: <CA+s+GJDdENtqQt1f+L5htuuyPxUxsq0prLQFBLirTjJz0nG1gw@mail.gmail.com>
<CAAS2fgRDmmv_EhUTRBfh8sBbCAoG_jcJeHE4fsKTHzOjoci4Gg@mail.gmail.com>
Date: Thu, 17 Apr 2014 09:39:33 +0200
Message-ID: <CA+s+GJBJgm8v5UZpwkF10UpP7-v3+DgsZZhedzu-6vad9cS2Qw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c319385d0e7f04f7382214
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Wagv4-0002CB-Te
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Warning message when running wallet in
Windows XP (or drop support?)
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, 17 Apr 2014 07:39:41 -0000
--001a11c319385d0e7f04f7382214
Content-Type: text/plain; charset=UTF-8
On Thu, Apr 17, 2014 at 12:06 AM, Gregory Maxwell <gmaxwell@gmail.com>wrote:
> Bringing the thread back on-topic:
>
Thanks.
> On Wed, Apr 16, 2014 at 1:14 AM, Wladimir <laanwj@gmail.com> wrote:
> > Hello,
> > Today I noticed that even my bank is warning people to not do internet
> > banking with Windows XP.
> > If it is no longer secure enough for online banking it's CERTAINLY not
> > secure enough to run a wallet (for a node only it would be ok-ish as they
> > have no keys to protect).
> > Any opinions on what to do here?
>
> I think eventually multi-wallet support will make it so that a wallet
> won't be created by default.
After the wallet split-off this will also be easier:
- Bitcoin Core Node
- Bitcoin Core Wallet
The node would be as compatible as possible with any OS in existence, but
the wallet can be more picky.
> Instead users would create-wallet, which
> would also give them options like using a HSM (e.g. trezor) or
> multisig secured wallet.
HSMs complicate this; I'm not even sure how this will work, are the Trezor
guys planning to contribute support for their device to wallets including
Bitcoin Core?
Hopefully by that time, everyone will have forgotten about XP already :)
Wladimir
--001a11c319385d0e7f04f7382214
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Apr 17, 2014 at 12:06 AM, Gregory Maxwell <span dir=3D"ltr"><<a =
href=3D"mailto:gmaxwell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>=
></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">Bringing the thread back =
on-topic:<br></blockquote><div><br></div><div>Thanks.<br></div><div>=C2=A0<=
/div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=3D"">
On Wed, Apr 16, 2014 at 1:14 AM, Wladimir <<a href=3D"mailto:laanwj@gmai=
l.com">laanwj@gmail.com</a>> wrote:<br>
</div><div class=3D"">> Hello,<br>
> Today I noticed that even my bank is warning people to not do internet=
<br>
> banking with Windows XP.<br>
> If it is no longer secure enough for online banking it's CERTAINLY=
not<br>
> secure enough to run a wallet (for a node only it would be ok-ish as t=
hey<br>
> have no keys to protect).<br>
> Any opinions on what to do here?<br>
<br>
</div>I think eventually multi-wallet support will make it so that a wallet=
<br>
won't be created by default. </blockquote><div><br></div><div>After the=
wallet split-off this will also be easier:<br></div><div><br>- Bitcoin Cor=
e Node<br></div><div>- Bitcoin Core Wallet<br></div><div><br></div><div>
The node would be as compatible as possible with any OS in existence, but t=
he wallet can be more picky.<br><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
Instead users would create-wallet, which<br>
would also give them options like using a HSM (e.g. trezor) or<br>
multisig secured wallet. =C2=A0</blockquote><div><br></div><div>HSMs compli=
cate this; I'm not even sure how this will work, are the Trezor guys pl=
anning to contribute support for their device to wallets including Bitcoin =
Core?<br>
<br></div><div>Hopefully by that time, everyone will have forgotten about X=
P already :)<br></div><br>Wladimir<br><br></div></div></div></div>
--001a11c319385d0e7f04f7382214--
|
