發(fā)信人: cloudsky (曉舟·軒轅明月), 信區(qū): Security 

標(biāo)  題: 關(guān)于win98的Bug 

發(fā)信站: 武漢白云黃鶴站 (Sat Jan 30 20:30:08 1999) , 站內(nèi)信件 

  

這一段時(shí)間沒(méi)有收訂閱的MailList,昨天夜里收了 

一下,貼些最近大家都在說(shuō)的東西. 

  

 Windows98 crashed by the packet which added a hand to the value of the 

IP header of the packet a little. (From now, the packet of this  structure 

is called with "oshare packet".) Because it isn't familiar, I don't know 

what kind of error happens concretely inside OS to the inside of Windows. 

But, ihl and tot_len. Then, it guesses that crash will happen by the 

value of frag_bit&frag_off. 

  

 But, because value is wrong, this "oshare packet" can't be transmitted 

to the outside of the network. This is here well, and it is here badly, 

too. But, even whose machine will be able to be killed in the same 

segment. 

  

 Before someone improves this program, MicroSoft should take a 

countermeasure immediately. 

  



 A Macintosh crashed by the "oshare packet" in the same way, too. 

But, it isn't realized by this program. It will be released soon. 

  

 Reboot hangs freely if it becomes blue screen when Windows98 receives 

a "oshare packet". When blue screen comes out, the function of the 

network can't be used any more after it. The error of TCP/IP is started 

in the case of the Macintosh, and the function of the network can't be 

used any more. 

  

 Is this phenomenon a bug? 

  

-- 

            我問(wèn)飄逝的風(fēng)：來(lái)遲了？ 

            風(fēng)感慨：是的，他們已經(jīng)宣戰(zhàn)。 

            我問(wèn)蘇醒的大地：還有希望么？ 

            大地揉了揉眼睛：還有，還有無(wú)數(shù)代的少年。 

            我問(wèn)長(zhǎng)空中的英魂：你們相信？ 

            英魂帶著笑意離去：相信，希望還在。