blocks|key|1152674|text|银行和电信中使用的几个协议-+including+the+SMS+protocol+-将年份编码为单字节中的BCD。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1152675|从2000到2009年，人们很容易犯下将年份解释为标准二进制数的错误，因为编码将是相同的：|1152676|Encoding++Binary-interpreted++BCD-interpreted
0x01++++++2001++++++++++++++++2001
0x02++++++2002++++++++++++++++2002
...
0x09++++++2009++++++++++++++++2009
0x10++++++2016++++++++++++++++2010
...|code-block|syntax|javascript|1152677|这很可能是Windows+Mobile+bug的原因。|1152678|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dreamfabric.com/sms/scts.html|1|http://en.wikipedia.org/wiki/Binary-coded_decimal^0|D|S|0|1I|3|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|14|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|15|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]]]

Several protocols used in banking and telecommunications <a href="http://www.dreamfabric.com/sms/scts.html" rel="nofollow noreferrer">- including the SMS protocol</a> - encode the year as <a href="http://en.wikipedia.org/wiki/Binary-coded_decimal" rel="nofollow noreferrer">BCD</a> in a single byte.

From 2000-2009 one could easily make the mistake of interpreting the year as a standard binary number since the encoding would be the same:

<pre><code>Encoding Binary-interpreted BCD-interpreted
0x01 2001 2001
0x02 2002 2002
...
0x09 2009 2009
0x10 2016 2010
...
</code></pre>

That is most probably the cause of the Windows Mobile bug.

blocks|key|1152427|text|SpamAssassin有一条规则，就是将太远的日期标记为垃圾邮件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1152428|/20[1-9][0-9]/|code-block|syntax|javascript|1152429|修复来得晚了几天，但它很简单：|1152430|/20[2-9][0-9]/|1152431|十年后再见。|1152432|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

SpamAssassin had a rule to mark dates too far in the future as spam:

<pre><code>/20[1-9][0-9]/
</code></pre>

The fix came a few days too late, but it's quite simple:

<pre><code>/20[2-9][0-9]/
</code></pre>

See you again in ten years.

blocks|key|1367487|text|我在工作中有一个系统，它使用一位数的年份字段。是。一位数。所以这个系统失败的原因是"2000“和"2010”是一样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1367488|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've got a system at work that uses a one digit year field. Yes. One digit. So the reason this system is failing is that "2000" is expressed the same as "2010".

blocks|key|1152380|text|我听说过的一个例子是，人们在没有仔细考虑的情况下就为Y2K做了快速修复。所以如果xx+<+10，则20xx否则为19xx。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1152381|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The one I heard about was quick fixes people did for Y2K without thinking it through. So if xx &lt; 10 then 20xx else 19xx.

blocks|key|1152468|text|这可能是因为年轻的开发人员在Y2K之后开始了他们的职业生涯，并使用1位数字来表示年份。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1152469|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It might be due to the young developers who started their careers after Y2K and are using 1 digit to represent the year.

blocks|key|1152539|text|上周末，我在一个网站上处理了一个2010年的小故障，这只是一个编码疏忽的结果。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1152540|有人认为，当列表只包含2009年前的项时，将列表项的值设置为当前的dateTime.year.Now()会是一个好主意。|1152541|ddlItem.findByText(DateTime.Now.Year.ToString())|code-block|syntax|javascript|1152542|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I took care of a little 2010 fail in a site last weekend, it was just the result of an oversight in coding though.

Someone thought it would be a good idea to set the value of a list item to the current dateTime.year.Now() when the list only contained items up to 2009.

<pre><code>ddlItem.findByText(DateTime.Now.Year.ToString())
</code></pre>

blocks|key|1152576|text|下面是norton+symantec端点保护的屏幕截图|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1152577|alt+text+http://img695.imageshack.us/img695/4500/152010112800am.jpg|offset|length|1152578|真的很好，没有人@+symantec通知他们的客户...在这篇文章发表之前：http://www.theregister.co.uk/2010/01/05/symantec_y2k10_bug/|1152579|entityMap|0|LINK|mutability|MUTABLE|url|http://img695.imageshack.us/img695/4500/152010112800am.jpg|1|http://www.theregister.co.uk/2010/01/05/symantec_y2k10_bug/^0|0|0|1V|0|0|12|1N|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Here is a screen shot of the norton symantec endpoint protection

<a href="http://img695.imageshack.us/img695/4500/152010112800am.jpg" rel="nofollow noreferrer">alt text http://img695.imageshack.us/img695/4500/152010112800am.jpg</a>

Really nice that no one @ symantec informed their customers...
Till the article was posted: <a href="http://www.theregister.co.uk/2010/01/05/symantec_y2k10_bug/" rel="nofollow noreferrer">http://www.theregister.co.uk/2010/01/05/symantec_y2k10_bug/</a>

blocks|key|1367726|text|它是在将一年分成两部分的组件中存在错误。第二部分用于比较，因此数字10不在基数10中，它在基数16中，这意味着它是0x10+=+16+(十六进制)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1367727|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It is that there is a bug in a component that splits the year in two parts. The second part is used in a comparison so that the digit 10 is not in base 10, it's in base 16 meaning that it's 0x10 = 16 (hex).

blocks|key|1367843|text|我用谷歌代码搜索find+y2010+bugs+in+open+source+software。我寻找了一个可以指示错误的特定模式(使用"200%25d“作为printf格式字符串)，并发现了几个具有该错误的项目。创造性地应用搜索模式可能会出现更多不同类型的bug。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1367844|entityMap|0|LINK|mutability|MUTABLE|url|http://ghewgill.livejournal.com/140515.html^0|8|13|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I used Google Code Search to <a href="http://ghewgill.livejournal.com/140515.html" rel="nofollow noreferrer">find y2010 bugs in open source software</a>. I looked for one particular pattern that would indicate a bug (use of "200%d" as a printf format string), and found several projects with that bug. Creative application of search patterns could probably turn up more different kinds of bugs.

There are a lot of reports of systems failing to understand the year 2010 but I've no idea why. Current systems I look after are working fine as far as I could tell but I'd like to know what the actual problem is to search better.

Could anyone shed some light on it please?

Edit: <a href="http://www.rte.ie/business/2010/0105/bug.html" rel="nofollow noreferrer">http://www.rte.ie/business/2010/0105/bug.html</a> - Information about it affecting credit cards in Germany

What is causing the 2010 bugs?

Windows

有很多关于系统不能理解2010年的报告，但我不知道为什么。据我所知，目前我所关注的系统运行良好，但我想知道更好地搜索的实际问题是什么。有没有人能解释一下？编辑： -影响德国信用卡的相关信息

问是什么导致了2010年的bug？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是什么导致了2010年的bug？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是什么导致了2010年的bug？
EN