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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WaKzo-0005f7-O9
for bitcoin-development@lists.sourceforge.net;
Wed, 16 Apr 2014 08:15:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.176 as permitted sender)
client-ip=209.85.213.176; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f176.google.com;
Received: from mail-ig0-f176.google.com ([209.85.213.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WaKzn-0008PH-Qs
for bitcoin-development@lists.sourceforge.net;
Wed, 16 Apr 2014 08:15:04 +0000
Received: by mail-ig0-f176.google.com with SMTP id uy17so753380igb.15
for <bitcoin-development@lists.sourceforge.net>;
Wed, 16 Apr 2014 01:14:58 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.120.66 with SMTP id la2mr28466419igb.1.1397636098541;
Wed, 16 Apr 2014 01:14:58 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Wed, 16 Apr 2014 01:14:58 -0700 (PDT)
Date: Wed, 16 Apr 2014 10:14:58 +0200
Message-ID: <CA+s+GJDdENtqQt1f+L5htuuyPxUxsq0prLQFBLirTjJz0nG1gw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7ba9796a2de4ba04f72483fd
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: 1WaKzn-0008PH-Qs
Subject: [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: Wed, 16 Apr 2014 08:15:04 -0000
--047d7ba9796a2de4ba04f72483fd
Content-Type: text/plain; charset=UTF-8
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? Just warn and allow the user to continue?
Redirect them to a 'Windows XP is dangerous' message on bitcoin.org?
(Microsoft uses http://windows.microsoft.com/en-us/windows/end-support-help)
The drawback of dropping XP support completely would be that a lot of
computers (especially in China and Russia etc) are still running XP, so
this could cause the network to lose nodes.
If you're maintainer of other wallet software: how are you handling this?
Are you going to drop XP support completely? If so, starting from when?
Regards,
Wladimir
--047d7ba9796a2de4ba04f72483fd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hello,<br><div class=3D"">
<div class=3D"">
<p>Today I noticed that even my bank is warning people to not d=
o internet banking with Windows XP.</p>
<p>If it is no longer secure enough for online banking it's CERTAINLY n=
ot secure enough to run a wallet (for a node only it would be ok-ish as the=
y have no keys to protect).</p></div>
</div>Any opinions on what to do here? Just warn and allow the user t=
o continue? Redirect them to a 'Windows XP is dangerous' message on=
<a href=3D"http://bitcoin.org">bitcoin.org</a>? (Microsoft uses <a href=3D=
"http://windows.microsoft.com/en-us/windows/end-support-help">http://window=
s.microsoft.com/en-us/windows/end-support-help</a>)<br>
<br></div><div>The drawback of dropping XP support completely would be that=
a lot of computers (especially in China and Russia etc) are still running =
XP, so this could cause the network to lose nodes.<br></div><div><br>If you=
're maintainer of other wallet software: how are you handling this?<br>
</div><div>Are you going to drop XP support completely? If so, starting fro=
m when?<br></div><div><br>Regards,<br></div>Wladimir<br><br></div>
--047d7ba9796a2de4ba04f72483fd--
|
