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
|
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 <bip@mattwhitlock.name>) id 1Wvgqk-0007qz-Px
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Jun 2014 05:49:58 +0000
X-ACL-Warn:
Received: from qmta03.westchester.pa.mail.comcast.net ([76.96.62.32])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Wvgqj-0004Y5-2o for bitcoin-development@lists.sourceforge.net;
Sat, 14 Jun 2014 05:49:58 +0000
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27])
by qmta03.westchester.pa.mail.comcast.net with comcast
id E5p71o0010bG4ec535prXn; Sat, 14 Jun 2014 05:49:51 +0000
Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f])
by omta03.westchester.pa.mail.comcast.net with comcast
id E5pq1o00D4VnV2P3P5prWL; Sat, 14 Jun 2014 05:49:51 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: Un Ix <slashdevnull@hotmail.com>
Date: Sat, 14 Jun 2014 01:49:49 -0400
Message-ID: <3528727.dtVK6SVFjZ@crushinator>
User-Agent: KMail/4.13.1 (Linux/3.12.20-gentoo; KDE/4.13.1; x86_64; ; )
In-Reply-To: <BLU402-EAS411D874A242EA16FA8D284BC6140@phx.gbl>
References: <CA+s+GJB0ZA0cUSsr=7X8y+YDTUXuXU8x03rX+OZdntwbn-_8TQ@mail.gmail.com>
<CA+s+GJAbSP77tab0neyhROTQuQ-hjjOtLJf+karAu5+2ENLwKA@mail.gmail.com>
<BLU402-EAS411D874A242EA16FA8D284BC6140@phx.gbl>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [76.96.62.32 listed in list.dnswl.org]
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: 1Wvgqj-0004Y5-2o
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
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: Sat, 14 Jun 2014 05:49:58 -0000
On Saturday, 14 June 2014, at 1:42 pm, Un Ix wrote:
> How about a prize for anyone who can spot any "malicious" strings within next hour?
I think it's more an issue of accidental breakage than any maliciousness. One character in the wrong place in a language bundle somewhere can make the difference between success and runtime failure, and it may not be immediately apparent when running in unaffected locales. This kind of problem isn't likely to result in data loss (or money loss, where money is data, is in Bitcoin), but it could be enough to necessitate scrapping the whole release, which would look bad and prompt users to question the dev team's quality control process.
|
