>"The cardinal rule in designing packet parsing routines is to assume the sender is malicious and has access to your source!"
Well, I actually apply this "rule" to all interface interactions, not just packet parsing. However, that was not my point. My point was the Micro$oft has a history of such things that usually result in a loss of market share for their competition. And now, it appears that Nokia may be following in Micro$oft's footprints.
If this really happened, was it an accident?
on
Flaming Cellphones
·
· Score: 1
This (from the article):
"In all cases it was caused by a replacement battery which was not a Nokia accessory. The manufacturers violated security requirements which should prevent it from heating up after short circuiting, for instance, after it was dropped."
reminds me of stuff like this( from http://www.bugnet.com/alerts/bugalert_11400.html):
'According to Netscape, the problem rests not with Communicator but instead with IIS. "What we found is that during the step up handshake IIS violates the SSL [Secure Socket Layer] 3 specification for performing this operation," explained Chris Nalls, senior product manager for client outbound marketing at Netscape. "It sends a request to communicate that's too short, which causes Communicator to crash." '
Was this truly an accident? Or, is Nokia intentionally "short circuiting" the battery for some reason?
Slashdot Mirror
They call it a replicator.
Don't waste your money buying a scanner. Teach the professor to use M$ Power Point or OO Impress. Those slide can easily be web published.
I am in the process of finishing up my third laptop purchase order set at work. Each and every laptop I order gets a Targus sport standard backpack or a Targus deluxe sport computer backpack to go with it. The Targus sport standard backpack is better for those who have a great deal of small items (e.g.: CDs, DVDs, etc...). The Targus deluxe sport computer backpack is better for those who have additional equipment and/or manuals to carry with them. Oh, by the way, I use my Targus delux sport computer backpack every day. It replaced my briefcase, notebook case, and duffle bag.
>"The cardinal rule in designing packet parsing routines is to assume the sender is malicious and has access to your source!"
Well, I actually apply this "rule" to all interface interactions, not just packet parsing. However, that was not my point. My point was the Micro$oft has a history of such things that usually result in a loss of market share for their competition. And now, it appears that Nokia may be following in Micro$oft's footprints.
"In all cases it was caused by a replacement battery which was not a Nokia accessory. The manufacturers violated security requirements which should prevent it from heating up after short circuiting, for instance, after it was dropped."
reminds me of stuff like this( from http://www.bugnet.com/alerts/bugalert_11400.html):
'According to Netscape, the problem rests not with Communicator but instead with IIS. "What we found is that during the step up handshake IIS violates the SSL [Secure Socket Layer] 3 specification for performing this operation," explained Chris Nalls, senior product manager for client outbound marketing at Netscape. "It sends a request to communicate that's too short, which causes Communicator to crash." '
Was this truly an accident? Or, is Nokia intentionally "short circuiting" the battery for some reason?