<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_07_03_1210222</id>
	<title>iPhone Vulnerability Yields Root Access Via SMS</title>
	<author>timothy</author>
	<datestamp>1246626060000</datestamp>
	<htmltext><a href="http://www.infoworld.com/" rel="nofollow">snydeq</a> writes <i>"Pwn2Own winner Charlie Miller has revealed <a href="http://infoworld.com/d/mobilize/apple-patching-serious-sms-vulnerability-iphone-934">an SMS vulnerability that could provide hackers with root access to the iPhone</a>. Malicious code sent by SMS to run on the phone could include commands to monitor location using GPS, turn on the phone's microphone to eavesdrop on conversations, or make the phone join a DDoS attack or botnet, Miller said. Miller did not provide detailed description of the SMS vulnerability, citing an agreement with Apple, which is working to fix the vulnerability in advance of Black Hat, where Miller plans to <a href="http://www.blackhat.com/html/bh-usa-09/bh-usa-09-speakers.html#Miller">discuss the attack in greater detail</a>. 'SMS is a great vector to attack the iPhone,' Miller said, as SMS can send binary code that the iPhone processes without user interaction. Sequences can be sent to the phone as multiple messages that are automatically reassembled, thereby surpassing individual SMS message limits of 140 bytes."</i></htmltext>
<tokenext>snydeq writes " Pwn2Own winner Charlie Miller has revealed an SMS vulnerability that could provide hackers with root access to the iPhone .
Malicious code sent by SMS to run on the phone could include commands to monitor location using GPS , turn on the phone 's microphone to eavesdrop on conversations , or make the phone join a DDoS attack or botnet , Miller said .
Miller did not provide detailed description of the SMS vulnerability , citing an agreement with Apple , which is working to fix the vulnerability in advance of Black Hat , where Miller plans to discuss the attack in greater detail .
'SMS is a great vector to attack the iPhone, ' Miller said , as SMS can send binary code that the iPhone processes without user interaction .
Sequences can be sent to the phone as multiple messages that are automatically reassembled , thereby surpassing individual SMS message limits of 140 bytes .
"</tokentext>
<sentencetext>snydeq writes "Pwn2Own winner Charlie Miller has revealed an SMS vulnerability that could provide hackers with root access to the iPhone.
Malicious code sent by SMS to run on the phone could include commands to monitor location using GPS, turn on the phone's microphone to eavesdrop on conversations, or make the phone join a DDoS attack or botnet, Miller said.
Miller did not provide detailed description of the SMS vulnerability, citing an agreement with Apple, which is working to fix the vulnerability in advance of Black Hat, where Miller plans to discuss the attack in greater detail.
'SMS is a great vector to attack the iPhone,' Miller said, as SMS can send binary code that the iPhone processes without user interaction.
Sequences can be sent to the phone as multiple messages that are automatically reassembled, thereby surpassing individual SMS message limits of 140 bytes.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570799</id>
	<title>Run up your bill too</title>
	<author>nurb432</author>
	<datestamp>1246630440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Nice little dDos attack device, with one hell of a use fee at the end of the month<nobr> <wbr></nobr>...</p></htmltext>
<tokenext>Nice little dDos attack device , with one hell of a use fee at the end of the month .. .</tokentext>
<sentencetext>Nice little dDos attack device, with one hell of a use fee at the end of the month ...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</id>
	<title>Well there's your problem!</title>
	<author>Anonymous</author>
	<datestamp>1246630560000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>"as SMS can send binary code that the iPhone processes without user interaction"</p><p>Why is it even possible to send raw binary?  Shouldn't it allow only a heavily-filtered subset of characters?</p></htmltext>
<tokenext>" as SMS can send binary code that the iPhone processes without user interaction " Why is it even possible to send raw binary ?
Should n't it allow only a heavily-filtered subset of characters ?</tokentext>
<sentencetext>"as SMS can send binary code that the iPhone processes without user interaction"Why is it even possible to send raw binary?
Shouldn't it allow only a heavily-filtered subset of characters?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571057</id>
	<title>Re:Well there's your problem!</title>
	<author>sam0737</author>
	<datestamp>1246632300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>"as SMS can send binary code that the iPhone processes without user interaction"</p><p>Why is it even possible to send raw binary?  Shouldn't it allow only a heavily-filtered subset of characters?</p></div><p>you mean allows only Chinese or Russian to pass through?</p><p>The unicode used is UTF-16, not UTF-8, which almost means every binary code is valid except for some range.</p></div>
	</htmltext>
<tokenext>" as SMS can send binary code that the iPhone processes without user interaction " Why is it even possible to send raw binary ?
Should n't it allow only a heavily-filtered subset of characters ? you mean allows only Chinese or Russian to pass through ? The unicode used is UTF-16 , not UTF-8 , which almost means every binary code is valid except for some range .</tokentext>
<sentencetext>"as SMS can send binary code that the iPhone processes without user interaction"Why is it even possible to send raw binary?
Shouldn't it allow only a heavily-filtered subset of characters?you mean allows only Chinese or Russian to pass through?The unicode used is UTF-16, not UTF-8, which almost means every binary code is valid except for some range.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571365</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>Anonymous</author>
	<datestamp>1246634280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually this type of exploit has been known to effect Nokia phones for awhile already. It seems only normal someone would figure out how to do it to an iPhone, (unless Apple was proactive in thwarting such an attack, which hasn't been the case)</p><p><a href="http://www.google.com/search?q=nokia+malformed+sms&amp;ie=utf-8&amp;oe=utf-8&amp;aq=t&amp;rls=com.ubuntu:en-US:unofficial&amp;client=firefox-a" title="google.com">http://www.google.com/search?q=nokia+malformed+sms&amp;ie=utf-8&amp;oe=utf-8&amp;aq=t&amp;rls=com.ubuntu:en-US:unofficial&amp;client=firefox-a</a> [google.com]</p></htmltext>
<tokenext>Actually this type of exploit has been known to effect Nokia phones for awhile already .
It seems only normal someone would figure out how to do it to an iPhone , ( unless Apple was proactive in thwarting such an attack , which has n't been the case ) http : //www.google.com/search ? q = nokia + malformed + sms&amp;ie = utf-8&amp;oe = utf-8&amp;aq = t&amp;rls = com.ubuntu : en-US : unofficial&amp;client = firefox-a [ google.com ]</tokentext>
<sentencetext>Actually this type of exploit has been known to effect Nokia phones for awhile already.
It seems only normal someone would figure out how to do it to an iPhone, (unless Apple was proactive in thwarting such an attack, which hasn't been the case)http://www.google.com/search?q=nokia+malformed+sms&amp;ie=utf-8&amp;oe=utf-8&amp;aq=t&amp;rls=com.ubuntu:en-US:unofficial&amp;client=firefox-a [google.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570841</id>
	<title>Next thing ...</title>
	<author>Anonymous</author>
	<datestamp>1246630800000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>Could the iPhone be jailbroken via SMS?</htmltext>
<tokenext>Could the iPhone be jailbroken via SMS ?</tokentext>
<sentencetext>Could the iPhone be jailbroken via SMS?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574847</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>omuls are tasty</author>
	<datestamp>1246613700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually the other FA says:</p><p><div class="quote"><p>The SMS vulnerability allows an attacker to run software code on the phone that is sent by SMS over a mobile operator's network.</p></div><p>So it's not really GP's fault.</p></div>
	</htmltext>
<tokenext>Actually the other FA says : The SMS vulnerability allows an attacker to run software code on the phone that is sent by SMS over a mobile operator 's network.So it 's not really GP 's fault .</tokentext>
<sentencetext>Actually the other FA says:The SMS vulnerability allows an attacker to run software code on the phone that is sent by SMS over a mobile operator's network.So it's not really GP's fault.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571079</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570959</id>
	<title>Re:Prevention/Defense</title>
	<author>Comatose51</author>
	<datestamp>1246631700000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>9-1-1

I'm going to disable SMS for now just to be safe so just call it and tell me.  If my hot blonde, high libido girlfriend picks up, say some obscene things to her.  Just act out your fantasy right over the phone.  She loves that.</htmltext>
<tokenext>9-1-1 I 'm going to disable SMS for now just to be safe so just call it and tell me .
If my hot blonde , high libido girlfriend picks up , say some obscene things to her .
Just act out your fantasy right over the phone .
She loves that .</tokentext>
<sentencetext>9-1-1

I'm going to disable SMS for now just to be safe so just call it and tell me.
If my hot blonde, high libido girlfriend picks up, say some obscene things to her.
Just act out your fantasy right over the phone.
She loves that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570767</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571495</id>
	<title>Re:Ouch!</title>
	<author>jdion</author>
	<datestamp>1246634940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever?</p></div><p>I would guess that this has more to do with the push features of the phone, including the new 'remote wipe' or 'find my phone' features if you happen to be using MobileMe. I would venture to guess the same functionality was provided to developers of any push application to execute commands for an applicable application.</p><p>I would venture to guess that the reason for this would be that SMS messages do not have any code signing, and in order to implement would have pushed out the deadline for Push based responses even further. Apple screwed the pooch by taking the path of least resistance, and gambled that this vulnerability wouldn't have been found for a good time (maybe iPhone OS 4.0).</p><p>Pure speculation on my part, but my $0.02.</p></div>
	</htmltext>
<tokenext>Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever ? I would guess that this has more to do with the push features of the phone , including the new 'remote wipe ' or 'find my phone ' features if you happen to be using MobileMe .
I would venture to guess the same functionality was provided to developers of any push application to execute commands for an applicable application.I would venture to guess that the reason for this would be that SMS messages do not have any code signing , and in order to implement would have pushed out the deadline for Push based responses even further .
Apple screwed the pooch by taking the path of least resistance , and gambled that this vulnerability would n't have been found for a good time ( maybe iPhone OS 4.0 ) .Pure speculation on my part , but my $ 0.02 .</tokentext>
<sentencetext>Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever?I would guess that this has more to do with the push features of the phone, including the new 'remote wipe' or 'find my phone' features if you happen to be using MobileMe.
I would venture to guess the same functionality was provided to developers of any push application to execute commands for an applicable application.I would venture to guess that the reason for this would be that SMS messages do not have any code signing, and in order to implement would have pushed out the deadline for Push based responses even further.
Apple screwed the pooch by taking the path of least resistance, and gambled that this vulnerability wouldn't have been found for a good time (maybe iPhone OS 4.0).Pure speculation on my part, but my $0.02.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574623</id>
	<title>Re:Outlook all over again?</title>
	<author>ae1294</author>
	<datestamp>1246612140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>How the hell can a format that's supposed to be passive plain text yield root access? Just receive and store the damn text, don't try to interpret it! If other apps want to peek into received messages and perform actions on that, fine, but this is just Outlook all over again!</p></div><p>Simple.. you send the message -</p><p>root<nobr> <wbr></nobr>...</p></div>
	</htmltext>
<tokenext>How the hell can a format that 's supposed to be passive plain text yield root access ?
Just receive and store the damn text , do n't try to interpret it !
If other apps want to peek into received messages and perform actions on that , fine , but this is just Outlook all over again ! Simple.. you send the message -root .. .</tokentext>
<sentencetext>How the hell can a format that's supposed to be passive plain text yield root access?
Just receive and store the damn text, don't try to interpret it!
If other apps want to peek into received messages and perform actions on that, fine, but this is just Outlook all over again!Simple.. you send the message -root ...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571303</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571303</id>
	<title>Outlook all over again?</title>
	<author>KlaymenDK</author>
	<datestamp>1246633800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How the hell can a format that's supposed to be passive plain text yield root access? Just receive and store the damn text, don't try to interpret it! If other apps want to peek into received messages and perform actions on that, fine, but this is just Outlook all over again!</p></htmltext>
<tokenext>How the hell can a format that 's supposed to be passive plain text yield root access ?
Just receive and store the damn text , do n't try to interpret it !
If other apps want to peek into received messages and perform actions on that , fine , but this is just Outlook all over again !</tokentext>
<sentencetext>How the hell can a format that's supposed to be passive plain text yield root access?
Just receive and store the damn text, don't try to interpret it!
If other apps want to peek into received messages and perform actions on that, fine, but this is just Outlook all over again!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693</id>
	<title>Ouch!</title>
	<author>thomasdn</author>
	<datestamp>1246629840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We do not know the details of this yet, but if this is really an "sms to root" exploit, it can be used for sms-based virusses that can spread very fast.</htmltext>
<tokenext>We do not know the details of this yet , but if this is really an " sms to root " exploit , it can be used for sms-based virusses that can spread very fast .</tokentext>
<sentencetext>We do not know the details of this yet, but if this is really an "sms to root" exploit, it can be used for sms-based virusses that can spread very fast.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572161</id>
	<title>Re:Well there's your problem!</title>
	<author>sp332</author>
	<datestamp>1246638720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You've never heard of the EICAR.COM virus?  (not the website, the win16, 100\% ASCII virus)</htmltext>
<tokenext>You 've never heard of the EICAR.COM virus ?
( not the website , the win16 , 100 \ % ASCII virus )</tokentext>
<sentencetext>You've never heard of the EICAR.COM virus?
(not the website, the win16, 100\% ASCII virus)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739</id>
	<title>Can't Carriers Stop this?</title>
	<author>Anonymous</author>
	<datestamp>1246630080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>So this is bad news for the iPhone but it seems like any carrier of the iPhone should want to implement a simple filter to remove any malicious SMSs from the system.</htmltext>
<tokenext>So this is bad news for the iPhone but it seems like any carrier of the iPhone should want to implement a simple filter to remove any malicious SMSs from the system .</tokentext>
<sentencetext>So this is bad news for the iPhone but it seems like any carrier of the iPhone should want to implement a simple filter to remove any malicious SMSs from the system.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570901</id>
	<title>Re:Ouch!</title>
	<author>rts008</author>
	<datestamp>1246631280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><nobr> <wbr></nobr></p><div class="quote"><p>...it can be used for sms-based virusses that can spread very fast.</p></div><p>A blackhat could have a field day with this on Twitter!</p></div>
	</htmltext>
<tokenext>...it can be used for sms-based virusses that can spread very fast.A blackhat could have a field day with this on Twitter !</tokentext>
<sentencetext> ...it can be used for sms-based virusses that can spread very fast.A blackhat could have a field day with this on Twitter!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570747</id>
	<title>Oh crap...</title>
	<author>bezking</author>
	<datestamp>1246630140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Now where did I leave my Dynatac???</htmltext>
<tokenext>Now where did I leave my Dynatac ? ?
?</tokentext>
<sentencetext>Now where did I leave my Dynatac??
?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570837</id>
	<title>i sense a disturbence in the force</title>
	<author>Anonymous</author>
	<datestamp>1246630800000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>it was as if 1000 apple fanbois cried out and then were silent...</htmltext>
<tokenext>it was as if 1000 apple fanbois cried out and then were silent.. .</tokentext>
<sentencetext>it was as if 1000 apple fanbois cried out and then were silent...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572401</id>
	<title>Re:Ouch!</title>
	<author>DustoneGT</author>
	<datestamp>1246640220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>When the fuck did we get ice cream?</htmltext>
<tokenext>When the fuck did we get ice cream ?</tokentext>
<sentencetext>When the fuck did we get ice cream?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571079</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>Anonymous</author>
	<datestamp>1246632420000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>if any of you had RTFA:</p><p><div class="quote"><p>allow a researcher to inject SMS messages into iPhone, Android, and Windows Mobile devices. This method does not use the carrier and so is free (and invisible to the carrier).<nobr> <wbr></nobr>.</p></div><p>the key is "this method does not use the carrier"</p><p>you're welcome</p></div>
	</htmltext>
<tokenext>if any of you had RTFA : allow a researcher to inject SMS messages into iPhone , Android , and Windows Mobile devices .
This method does not use the carrier and so is free ( and invisible to the carrier ) .
.the key is " this method does not use the carrier " you 're welcome</tokentext>
<sentencetext>if any of you had RTFA:allow a researcher to inject SMS messages into iPhone, Android, and Windows Mobile devices.
This method does not use the carrier and so is free (and invisible to the carrier).
.the key is "this method does not use the carrier"you're welcome
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570685</id>
	<title>iPhone needs to cool down before you can use it</title>
	<author>Anonymous</author>
	<datestamp>1246629780000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Shit hardware. Shit software. Apple: think shit</p></htmltext>
<tokenext>Shit hardware .
Shit software .
Apple : think shit</tokentext>
<sentencetext>Shit hardware.
Shit software.
Apple: think shit</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571217</id>
	<title>Re:i sense a disturbence in the force</title>
	<author>Oktober Sunset</author>
	<datestamp>1246633260000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>1</modscore>
	<htmltext>if only...  even if every mac on the planet turned into a robot and killed a baby before collapsing into a pile of toxic debris, it would only shut the fanboys up for 5 minutes before they resumed bleating on about garage band and iphoto...</htmltext>
<tokenext>if only... even if every mac on the planet turned into a robot and killed a baby before collapsing into a pile of toxic debris , it would only shut the fanboys up for 5 minutes before they resumed bleating on about garage band and iphoto.. .</tokentext>
<sentencetext>if only...  even if every mac on the planet turned into a robot and killed a baby before collapsing into a pile of toxic debris, it would only shut the fanboys up for 5 minutes before they resumed bleating on about garage band and iphoto...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570837</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575005</id>
	<title>Re:Ouch!</title>
	<author>numbski</author>
	<datestamp>1246614780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The same person that thought it was good to have automatic voicemail notification.  Most modern GSM phones have a special set of binary SMS that come through for various purposes, one being voicemail notification.</p></htmltext>
<tokenext>The same person that thought it was good to have automatic voicemail notification .
Most modern GSM phones have a special set of binary SMS that come through for various purposes , one being voicemail notification .</tokentext>
<sentencetext>The same person that thought it was good to have automatic voicemail notification.
Most modern GSM phones have a special set of binary SMS that come through for various purposes, one being voicemail notification.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573355</id>
	<title>Sounds more like an FBI Backdoor than an exploit</title>
	<author>Anonymous</author>
	<datestamp>1246646100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sounds more like an FBI Backdoor than an exploit.</p><p>Oh but dont worry, the federal government has your interest at heart.</p></htmltext>
<tokenext>Sounds more like an FBI Backdoor than an exploit.Oh but dont worry , the federal government has your interest at heart .</tokentext>
<sentencetext>Sounds more like an FBI Backdoor than an exploit.Oh but dont worry, the federal government has your interest at heart.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573733</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>Anonymous</author>
	<datestamp>1246648560000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>It's not the carrier's responsibility to look at all SMS messages going through their system and filter them out, it's the iPhone's responsibility to not execute untrusted code in the first place.  If this was a Microsoft device that's exactly what people would be saying.</p></htmltext>
<tokenext>It 's not the carrier 's responsibility to look at all SMS messages going through their system and filter them out , it 's the iPhone 's responsibility to not execute untrusted code in the first place .
If this was a Microsoft device that 's exactly what people would be saying .</tokentext>
<sentencetext>It's not the carrier's responsibility to look at all SMS messages going through their system and filter them out, it's the iPhone's responsibility to not execute untrusted code in the first place.
If this was a Microsoft device that's exactly what people would be saying.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570957</id>
	<title>At least SOMEBODY has full access to my iPhone!</title>
	<author>just fiddling around</author>
	<datestamp>1246631700000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>That's just great.   I can't use all the features of the iPhone because it is crippled by the providers, but any dumbass can get root by SMS?</p><p>If I had "bought" one (I consider the current way of getting it as rent-to-own), I would be pissed.</p></htmltext>
<tokenext>That 's just great .
I ca n't use all the features of the iPhone because it is crippled by the providers , but any dumbass can get root by SMS ? If I had " bought " one ( I consider the current way of getting it as rent-to-own ) , I would be pissed .</tokentext>
<sentencetext>That's just great.
I can't use all the features of the iPhone because it is crippled by the providers, but any dumbass can get root by SMS?If I had "bought" one (I consider the current way of getting it as rent-to-own), I would be pissed.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574063</id>
	<title>Re:Seems to affect other smart phones as well ...</title>
	<author>Hurricane78</author>
	<datestamp>1246651020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Apparently no Symbian devices. I know that Nokia allows for apps to be installed in a way, in which they somehow go trough the generic message inbox (the one that gets SMS, e-Mail, etc)<br>But the Symbian devices lets you jump trough at least two hoops before it gets installed. First you have to agree to run the installer. And then you have to agree for the installer having the right to install anything that will survive a reboot, without the usually needed certificate.</p></htmltext>
<tokenext>Apparently no Symbian devices .
I know that Nokia allows for apps to be installed in a way , in which they somehow go trough the generic message inbox ( the one that gets SMS , e-Mail , etc ) But the Symbian devices lets you jump trough at least two hoops before it gets installed .
First you have to agree to run the installer .
And then you have to agree for the installer having the right to install anything that will survive a reboot , without the usually needed certificate .</tokentext>
<sentencetext>Apparently no Symbian devices.
I know that Nokia allows for apps to be installed in a way, in which they somehow go trough the generic message inbox (the one that gets SMS, e-Mail, etc)But the Symbian devices lets you jump trough at least two hoops before it gets installed.
First you have to agree to run the installer.
And then you have to agree for the installer having the right to install anything that will survive a reboot, without the usually needed certificate.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571067</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572059</id>
	<title>Re:Well there's your problem!</title>
	<author>noelhenson</author>
	<datestamp>1246638120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Shouldn't SMS messages only contain SMS <i>TEXT</i>?! The worst that should happen is that you have a binary SMS message in your inbox.</htmltext>
<tokenext>Should n't SMS messages only contain SMS TEXT ? !
The worst that should happen is that you have a binary SMS message in your inbox .</tokentext>
<sentencetext>Shouldn't SMS messages only contain SMS TEXT?!
The worst that should happen is that you have a binary SMS message in your inbox.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575293</id>
	<title>Re:Next thing ...</title>
	<author>Anonymous</author>
	<datestamp>1246616940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You jest, but I'm seriously interested in this aspect of it... Remember that one jailbreak method where the user visited a website with a specially crafted image file to jailbreak/unlock and you were able to install Installer.app back in the OS 1.1.2 days? It did all that and then closed the vulnerability when it was finished. Pretty nifty too.</p></htmltext>
<tokenext>You jest , but I 'm seriously interested in this aspect of it... Remember that one jailbreak method where the user visited a website with a specially crafted image file to jailbreak/unlock and you were able to install Installer.app back in the OS 1.1.2 days ?
It did all that and then closed the vulnerability when it was finished .
Pretty nifty too .</tokentext>
<sentencetext>You jest, but I'm seriously interested in this aspect of it... Remember that one jailbreak method where the user visited a website with a specially crafted image file to jailbreak/unlock and you were able to install Installer.app back in the OS 1.1.2 days?
It did all that and then closed the vulnerability when it was finished.
Pretty nifty too.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570841</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572587</id>
	<title>Re:SMS limit isn't 140 characters</title>
	<author>admiral201</author>
	<datestamp>1246641540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>ISTR that SMS is 160 characters, but those characters are 7-bit characters, making the total SMS message length in bytes shorter (about 140 bytes).</p><p>Hence, if you're sending 8-bit ("binary") data, it would be limited to those same 140 bytes.</p></htmltext>
<tokenext>ISTR that SMS is 160 characters , but those characters are 7-bit characters , making the total SMS message length in bytes shorter ( about 140 bytes ) .Hence , if you 're sending 8-bit ( " binary " ) data , it would be limited to those same 140 bytes .</tokentext>
<sentencetext>ISTR that SMS is 160 characters, but those characters are 7-bit characters, making the total SMS message length in bytes shorter (about 140 bytes).Hence, if you're sending 8-bit ("binary") data, it would be limited to those same 140 bytes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571123</id>
	<title>hypocracy</title>
	<author>gripusa</author>
	<datestamp>1246632780000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext>I am surprised to see the slashdotter's  response, if this is somehow Micorsoft , i might heard long list of moanings that microsoft is this and that and now look if the culprit is their hearty [Pine]Apple this is just a joke or laugh<nobr> <wbr></nobr>...</htmltext>
<tokenext>I am surprised to see the slashdotter 's response , if this is somehow Micorsoft , i might heard long list of moanings that microsoft is this and that and now look if the culprit is their hearty [ Pine ] Apple this is just a joke or laugh .. .</tokentext>
<sentencetext>I am surprised to see the slashdotter's  response, if this is somehow Micorsoft , i might heard long list of moanings that microsoft is this and that and now look if the culprit is their hearty [Pine]Apple this is just a joke or laugh ...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573521</id>
	<title>Re:Ouch!</title>
	<author>AcidPenguin9873</author>
	<datestamp>1246647180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Obviously I don't know the details of the exploit, but no phone software would willingly execute code that they have no control over.  These exploits take advantage of security bugs in the phone software to get them to execute code.</p><p>A simple naive example is the classic <a href="http://en.wikipedia.org/wiki/Stack\_buffer\_overflow" title="wikipedia.org">stack buffer overflow</a> [wikipedia.org]. I might send a malformed SMS that encodes a 200-byte message (140 bytes is the byte limit for SMS). If the software that processes the SMS didn't check that the byte count is less than 140, it might happily write those 200 bytes into a stack-allocated 160-byte character array (160 being the character limit for SMS).  Now you've overflowed that fixed-size 160-byte buffer by 40 bytes.  Some of those 40 bytes are going to scribble over the return address of the called function.  When the function returns, you now are controlling where it returns to.  That's the "exploit".  (This example is probably way too simple and is likely NOT how the actual phone exploit works; it is just to illustrate the point.)</p><p>The second part of the exploit is the "payload", which is located somewhere else in that extra 40 bytes. If you can do it right, you can construct your exploit such that you point the return address *into* the payload, and now when the function returns, the payload is where you're executing from. You have now effectively gained control of the phone, because it's executing code that you gave it. It didn't willingly execute it for you, you took advantage of a security flaw to do so.</p></htmltext>
<tokenext>Obviously I do n't know the details of the exploit , but no phone software would willingly execute code that they have no control over .
These exploits take advantage of security bugs in the phone software to get them to execute code.A simple naive example is the classic stack buffer overflow [ wikipedia.org ] .
I might send a malformed SMS that encodes a 200-byte message ( 140 bytes is the byte limit for SMS ) .
If the software that processes the SMS did n't check that the byte count is less than 140 , it might happily write those 200 bytes into a stack-allocated 160-byte character array ( 160 being the character limit for SMS ) .
Now you 've overflowed that fixed-size 160-byte buffer by 40 bytes .
Some of those 40 bytes are going to scribble over the return address of the called function .
When the function returns , you now are controlling where it returns to .
That 's the " exploit " .
( This example is probably way too simple and is likely NOT how the actual phone exploit works ; it is just to illustrate the point .
) The second part of the exploit is the " payload " , which is located somewhere else in that extra 40 bytes .
If you can do it right , you can construct your exploit such that you point the return address * into * the payload , and now when the function returns , the payload is where you 're executing from .
You have now effectively gained control of the phone , because it 's executing code that you gave it .
It did n't willingly execute it for you , you took advantage of a security flaw to do so .</tokentext>
<sentencetext>Obviously I don't know the details of the exploit, but no phone software would willingly execute code that they have no control over.
These exploits take advantage of security bugs in the phone software to get them to execute code.A simple naive example is the classic stack buffer overflow [wikipedia.org].
I might send a malformed SMS that encodes a 200-byte message (140 bytes is the byte limit for SMS).
If the software that processes the SMS didn't check that the byte count is less than 140, it might happily write those 200 bytes into a stack-allocated 160-byte character array (160 being the character limit for SMS).
Now you've overflowed that fixed-size 160-byte buffer by 40 bytes.
Some of those 40 bytes are going to scribble over the return address of the called function.
When the function returns, you now are controlling where it returns to.
That's the "exploit".
(This example is probably way too simple and is likely NOT how the actual phone exploit works; it is just to illustrate the point.
)The second part of the exploit is the "payload", which is located somewhere else in that extra 40 bytes.
If you can do it right, you can construct your exploit such that you point the return address *into* the payload, and now when the function returns, the payload is where you're executing from.
You have now effectively gained control of the phone, because it's executing code that you gave it.
It didn't willingly execute it for you, you took advantage of a security flaw to do so.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571413</id>
	<title>Re:Well there's your problem!</title>
	<author>CrashandDie</author>
	<datestamp>1246634520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yes, because nobody has ever thought of something like base64 to represent binary with printable characters...</htmltext>
<tokenext>Yes , because nobody has ever thought of something like base64 to represent binary with printable characters.. .</tokentext>
<sentencetext>Yes, because nobody has ever thought of something like base64 to represent binary with printable characters...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573571</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>Mista2</author>
	<datestamp>1246647420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And why not add some antivirus and a firewall on the phone, and make it a bit bigger, say like a netbook... damn, feature creep again 8)</p></htmltext>
<tokenext>And why not add some antivirus and a firewall on the phone , and make it a bit bigger , say like a netbook... damn , feature creep again 8 )</tokentext>
<sentencetext>And why not add some antivirus and a firewall on the phone, and make it a bit bigger, say like a netbook... damn, feature creep again 8)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570759</id>
	<title>Great</title>
	<author>Anonymous</author>
	<datestamp>1246630260000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Next thing you know, someone discovers some fault in the battery configuration and he can get Nokia to pay him to blow up every single iPhone user on the planet. Awesome.</p></htmltext>
<tokenext>Next thing you know , someone discovers some fault in the battery configuration and he can get Nokia to pay him to blow up every single iPhone user on the planet .
Awesome .</tokentext>
<sentencetext>Next thing you know, someone discovers some fault in the battery configuration and he can get Nokia to pay him to blow up every single iPhone user on the planet.
Awesome.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571637</id>
	<title>Re:SMS limit isn't 140 characters</title>
	<author>Anonymous</author>
	<datestamp>1246635900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Several countries also have 140 character limits because the carriers use an 8-bit character set, in some countries they use a 7-bit character set and hence get the "extra" 20 letters per message.</p></htmltext>
<tokenext>Several countries also have 140 character limits because the carriers use an 8-bit character set , in some countries they use a 7-bit character set and hence get the " extra " 20 letters per message .</tokentext>
<sentencetext>Several countries also have 140 character limits because the carriers use an 8-bit character set, in some countries they use a 7-bit character set and hence get the "extra" 20 letters per message.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572863</id>
	<title>Re:Well there's your problem!</title>
	<author>da\_matta</author>
	<datestamp>1246643040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Text messaging is actually just one service of the SMS bearer, and it can also used for sending binary content like configuration messages. There are also many variations (e.g. charactersets), which are defined be the <a href="http://www.dreamfabric.com/sms/" title="dreamfabric.com">PDU headers</a> [dreamfabric.com]. Checkout the protocol identifiers for available services.

<br> <br>This sounds like a classical failure to correctly validate the data or handle some unsupported combination resulting in a crash or a buffer overflow. What is amazing is that they can fit an actual payload to the message...</htmltext>
<tokenext>Text messaging is actually just one service of the SMS bearer , and it can also used for sending binary content like configuration messages .
There are also many variations ( e.g .
charactersets ) , which are defined be the PDU headers [ dreamfabric.com ] .
Checkout the protocol identifiers for available services .
This sounds like a classical failure to correctly validate the data or handle some unsupported combination resulting in a crash or a buffer overflow .
What is amazing is that they can fit an actual payload to the message.. .</tokentext>
<sentencetext>Text messaging is actually just one service of the SMS bearer, and it can also used for sending binary content like configuration messages.
There are also many variations (e.g.
charactersets), which are defined be the PDU headers [dreamfabric.com].
Checkout the protocol identifiers for available services.
This sounds like a classical failure to correctly validate the data or handle some unsupported combination resulting in a crash or a buffer overflow.
What is amazing is that they can fit an actual payload to the message...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575955</id>
	<title>Telling Apple won't go well...</title>
	<author>Anonymous</author>
	<datestamp>1246622760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>     Telling Apple about this first will not go well..  Here's almost a 100\% chance of what will happen:</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1) Apple will sit on their hands and do nothing, or work to fix this bug at a GLACIAL pace. They will not get it done before BlackHat.</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2) They will then legally threaten the discoverer into not presenting.</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3) They will then call up LEGIONS of Apple fanbois to lie and claim "Well, he didn't present because he didn't have an exploit!  This bug doesn't exist!"</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 4) When they get around for it they will release a patch, saying it adds features rather than fixing security holes.</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This is the EXACT tact Apple used for at least the wifi buffer overflows found a few years ago (which were in fact found to work on nearly every card on the market.).  Apple fanbois STILL falsely claim the flaw was non-exploitable  on Apples, even though it was exploitable on everything else that had a similar flaw.</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Apple has shown themselves to be a bad actor regarding security flaws.  If I find one, you all will be the FIRST to know, and Apple can find out whenever their employees get around to reading about it on the blogosphere.</p></htmltext>
<tokenext>Telling Apple about this first will not go well.. Here 's almost a 100 \ % chance of what will happen :           1 ) Apple will sit on their hands and do nothing , or work to fix this bug at a GLACIAL pace .
They will not get it done before BlackHat .
          2 ) They will then legally threaten the discoverer into not presenting .
          3 ) They will then call up LEGIONS of Apple fanbois to lie and claim " Well , he did n't present because he did n't have an exploit !
This bug does n't exist !
"           4 ) When they get around for it they will release a patch , saying it adds features rather than fixing security holes .
            This is the EXACT tact Apple used for at least the wifi buffer overflows found a few years ago ( which were in fact found to work on nearly every card on the market. ) .
Apple fanbois STILL falsely claim the flaw was non-exploitable on Apples , even though it was exploitable on everything else that had a similar flaw .
          Apple has shown themselves to be a bad actor regarding security flaws .
If I find one , you all will be the FIRST to know , and Apple can find out whenever their employees get around to reading about it on the blogosphere .</tokentext>
<sentencetext>     Telling Apple about this first will not go well..  Here's almost a 100\% chance of what will happen:
          1) Apple will sit on their hands and do nothing, or work to fix this bug at a GLACIAL pace.
They will not get it done before BlackHat.
          2) They will then legally threaten the discoverer into not presenting.
          3) They will then call up LEGIONS of Apple fanbois to lie and claim "Well, he didn't present because he didn't have an exploit!
This bug doesn't exist!
"
          4) When they get around for it they will release a patch, saying it adds features rather than fixing security holes.
            This is the EXACT tact Apple used for at least the wifi buffer overflows found a few years ago (which were in fact found to work on nearly every card on the market.).
Apple fanbois STILL falsely claim the flaw was non-exploitable  on Apples, even though it was exploitable on everything else that had a similar flaw.
          Apple has shown themselves to be a bad actor regarding security flaws.
If I find one, you all will be the FIRST to know, and Apple can find out whenever their employees get around to reading about it on the blogosphere.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570931</id>
	<title>Jobs to the rescue</title>
	<author>Anonymous</author>
	<datestamp>1246631460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Surely, the awesomeness of the iPhone protects it users? No? Hmm.. wait, but you know, it is *shiny*, and does get very hot, so hot you can't hold it. Yeah, this phone is the biz.<br>SMS crashes phone? Epic Fail Apple. What sort of crappy programmer doesn't know how to handle and parse text safely.</p></htmltext>
<tokenext>Surely , the awesomeness of the iPhone protects it users ?
No ? Hmm.. wait , but you know , it is * shiny * , and does get very hot , so hot you ca n't hold it .
Yeah , this phone is the biz.SMS crashes phone ?
Epic Fail Apple .
What sort of crappy programmer does n't know how to handle and parse text safely .</tokentext>
<sentencetext>Surely, the awesomeness of the iPhone protects it users?
No? Hmm.. wait, but you know, it is *shiny*, and does get very hot, so hot you can't hold it.
Yeah, this phone is the biz.SMS crashes phone?
Epic Fail Apple.
What sort of crappy programmer doesn't know how to handle and parse text safely.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571581</id>
	<title>Apples Newest Product...</title>
	<author>Sfing\_ter</author>
	<datestamp>1246635540000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>The iPwn. Be the first on your network to get iPwned.</p><p>Pwn Different!</p><p>Just Pwn.</p><p><a href="http://www.screenprintingasap.com/EBAY/ipwn/ipwn\_a.jpg" title="screenprintingasap.com">http://www.screenprintingasap.com/EBAY/ipwn/ipwn\_a.jpg</a> [screenprintingasap.com]</p></htmltext>
<tokenext>The iPwn .
Be the first on your network to get iPwned.Pwn Different ! Just Pwn.http : //www.screenprintingasap.com/EBAY/ipwn/ipwn \ _a.jpg [ screenprintingasap.com ]</tokentext>
<sentencetext>The iPwn.
Be the first on your network to get iPwned.Pwn Different!Just Pwn.http://www.screenprintingasap.com/EBAY/ipwn/ipwn\_a.jpg [screenprintingasap.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571705</id>
	<title>Re:Ouch!</title>
	<author>FlyingBishop</author>
	<datestamp>1246636200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The second link describes a general vulnerability in the SMS protocol. It sounds like you may need to have a wireless transmitter in general proximity to the phone. You then send a spoofed ("fuzzed") message which the phone interprets poorly, with the end result that it executes some code you have chosen.</p><p>It also doesn't necessarily look like this would result in the sort of viral behavior we usually see from exploits, since the SMS does not show up on the carrier's radar (which I interpret to mean that it cannot pass through the carrier tower.)</p><p>Though I don't know if phone-to-phone direct could be used to do this.</p></htmltext>
<tokenext>The second link describes a general vulnerability in the SMS protocol .
It sounds like you may need to have a wireless transmitter in general proximity to the phone .
You then send a spoofed ( " fuzzed " ) message which the phone interprets poorly , with the end result that it executes some code you have chosen.It also does n't necessarily look like this would result in the sort of viral behavior we usually see from exploits , since the SMS does not show up on the carrier 's radar ( which I interpret to mean that it can not pass through the carrier tower .
) Though I do n't know if phone-to-phone direct could be used to do this .</tokentext>
<sentencetext>The second link describes a general vulnerability in the SMS protocol.
It sounds like you may need to have a wireless transmitter in general proximity to the phone.
You then send a spoofed ("fuzzed") message which the phone interprets poorly, with the end result that it executes some code you have chosen.It also doesn't necessarily look like this would result in the sort of viral behavior we usually see from exploits, since the SMS does not show up on the carrier's radar (which I interpret to mean that it cannot pass through the carrier tower.
)Though I don't know if phone-to-phone direct could be used to do this.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570767</id>
	<title>Prevention/Defense</title>
	<author>Anonymous</author>
	<datestamp>1246630320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>If any of you iPhone users wants to know how to prevent this attack, please reply with your cellphone number and I will TXT you the details.</p><p>You're welcome!</p></htmltext>
<tokenext>If any of you iPhone users wants to know how to prevent this attack , please reply with your cellphone number and I will TXT you the details.You 're welcome !</tokentext>
<sentencetext>If any of you iPhone users wants to know how to prevent this attack, please reply with your cellphone number and I will TXT you the details.You're welcome!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571645</id>
	<title>Depends how you define characters</title>
	<author>multipart/mixed</author>
	<datestamp>1246635960000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>And the case of binary data, you're dead wrong.</p><p>GSM SMS payload is 140 8-bit characters, or bytes, depending how you look at it.</p><p>The default SMS text encoding format uses 7-bits, and employs a bit-shifting algorithm to pack 160 7-bit characters in to 140 bytes. Binary formats can't use this compression, as, well, they need all eight bits.</p></htmltext>
<tokenext>And the case of binary data , you 're dead wrong.GSM SMS payload is 140 8-bit characters , or bytes , depending how you look at it.The default SMS text encoding format uses 7-bits , and employs a bit-shifting algorithm to pack 160 7-bit characters in to 140 bytes .
Binary formats ca n't use this compression , as , well , they need all eight bits .</tokentext>
<sentencetext>And the case of binary data, you're dead wrong.GSM SMS payload is 140 8-bit characters, or bytes, depending how you look at it.The default SMS text encoding format uses 7-bits, and employs a bit-shifting algorithm to pack 160 7-bit characters in to 140 bytes.
Binary formats can't use this compression, as, well, they need all eight bits.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575741</id>
	<title>Re:</title>
	<author>clint999</author>
	<datestamp>1246620600000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><strong>Not that difficult. Shall I name a few device names?- Pharos 535v- HP iPaq 111- HP iPaq 211 (would go for that one, 4" VGA screen rocks)Motorola/Symbol still make lots of them but they are way too expensive, and not as robust as they look like.The used market should be huge.And by the way, is it really the case that you cannot buy a Windows Mobile phone without a contract? In Germany it wouldn't be a problem at all.</strong></htmltext>
<tokenext>Not that difficult .
Shall I name a few device names ? - Pharos 535v- HP iPaq 111- HP iPaq 211 ( would go for that one , 4 " VGA screen rocks ) Motorola/Symbol still make lots of them but they are way too expensive , and not as robust as they look like.The used market should be huge.And by the way , is it really the case that you can not buy a Windows Mobile phone without a contract ?
In Germany it would n't be a problem at all .</tokentext>
<sentencetext>Not that difficult.
Shall I name a few device names?- Pharos 535v- HP iPaq 111- HP iPaq 211 (would go for that one, 4" VGA screen rocks)Motorola/Symbol still make lots of them but they are way too expensive, and not as robust as they look like.The used market should be huge.And by the way, is it really the case that you cannot buy a Windows Mobile phone without a contract?
In Germany it wouldn't be a problem at all.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573483</id>
	<title>Re:Ouch!</title>
	<author>sgt\_doom</author>
	<datestamp>1246646880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>"Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever?"</i> </p><p>Master control?  The Illuminati?  World Domination Society?  Those Free Mason chaps?  Hank Paulson, wherever the f**k he is?  Goldman Sachs?  JPMorgan Chase?  Morgan Stanley?  InterContinental Exchange?  ICE US Trust? DTCC?</p></htmltext>
<tokenext>" Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever ?
" Master control ?
The Illuminati ?
World Domination Society ?
Those Free Mason chaps ?
Hank Paulson , wherever the f * * k he is ?
Goldman Sachs ?
JPMorgan Chase ?
Morgan Stanley ?
InterContinental Exchange ?
ICE US Trust ?
DTCC ?</tokentext>
<sentencetext>"Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever?
" Master control?
The Illuminati?
World Domination Society?
Those Free Mason chaps?
Hank Paulson, wherever the f**k he is?
Goldman Sachs?
JPMorgan Chase?
Morgan Stanley?
InterContinental Exchange?
ICE US Trust?
DTCC?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570743</id>
	<title>iPhone Vulnerability Yields Root Access Via SMS</title>
	<author>Anonymous</author>
	<datestamp>1246630080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>"...Malicious code sent by SMS to run on the phone could include commands to monitor location using GPS, turn on the phone's microphone to eavesdrop on conversations,..."</p><p>Cool now my wife can have that  iphone she always wanted.</p></htmltext>
<tokenext>" ...Malicious code sent by SMS to run on the phone could include commands to monitor location using GPS , turn on the phone 's microphone to eavesdrop on conversations,... " Cool now my wife can have that iphone she always wanted .</tokentext>
<sentencetext>"...Malicious code sent by SMS to run on the phone could include commands to monitor location using GPS, turn on the phone's microphone to eavesdrop on conversations,..."Cool now my wife can have that  iphone she always wanted.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571393</id>
	<title>Re:Ouch!</title>
	<author>Nerdfest</author>
	<datestamp>1246634400000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>That would be Steve Jobs<nobr> <wbr></nobr>... but he's a sick man.</htmltext>
<tokenext>That would be Steve Jobs ... but he 's a sick man .</tokentext>
<sentencetext>That would be Steve Jobs ... but he's a sick man.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571411</id>
	<title>Re:Well there's your problem!</title>
	<author>Anonymous</author>
	<datestamp>1246634520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I don't have an iPhone, so I'm not sure if you can do this, but my Blackberry can send SMS's with embedded pictures/videos/sounds. Commonally called MMS. According to wikipedia, its an exension of the SMS standard. I would assume this is where the vulnerabilities lie.
<br> <br>
<a href="http://en.wikipedia.org/wiki/Multimedia\_Messaging\_Service" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Multimedia\_Messaging\_Service</a> [wikipedia.org]</htmltext>
<tokenext>I do n't have an iPhone , so I 'm not sure if you can do this , but my Blackberry can send SMS 's with embedded pictures/videos/sounds .
Commonally called MMS .
According to wikipedia , its an exension of the SMS standard .
I would assume this is where the vulnerabilities lie .
http : //en.wikipedia.org/wiki/Multimedia \ _Messaging \ _Service [ wikipedia.org ]</tokentext>
<sentencetext>I don't have an iPhone, so I'm not sure if you can do this, but my Blackberry can send SMS's with embedded pictures/videos/sounds.
Commonally called MMS.
According to wikipedia, its an exension of the SMS standard.
I would assume this is where the vulnerabilities lie.
http://en.wikipedia.org/wiki/Multimedia\_Messaging\_Service [wikipedia.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571247</id>
	<title>Re:Well there's your problem!</title>
	<author>Anonymous</author>
	<datestamp>1246633440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>SMS is a hack, it's actually a control channel that was eventually repackaged and resold as the now prevalent SMS.</p><p>I guess they forgot to disable the control functionality when they stopped using the control channel for actual, you know, control messages.</p></htmltext>
<tokenext>SMS is a hack , it 's actually a control channel that was eventually repackaged and resold as the now prevalent SMS.I guess they forgot to disable the control functionality when they stopped using the control channel for actual , you know , control messages .</tokentext>
<sentencetext>SMS is a hack, it's actually a control channel that was eventually repackaged and resold as the now prevalent SMS.I guess they forgot to disable the control functionality when they stopped using the control channel for actual, you know, control messages.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</id>
	<title>Re:Ouch!</title>
	<author>Anonymous</author>
	<datestamp>1246630800000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever?</p></htmltext>
<tokenext>Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever ?</tokentext>
<sentencetext>Who the fuck though it would be a good idea to automatically execute the content of a message you have no control over whatsoever?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572193</id>
	<title>Re:Prevention/Defense</title>
	<author>Anonymous</author>
	<datestamp>1246638900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>202-456-1111</p><p>Just dumped my crackberry for a 3GS. I need to know ASAP.</p><p>Thanks!</p><p>---Barack</p></htmltext>
<tokenext>202-456-1111Just dumped my crackberry for a 3GS .
I need to know ASAP.Thanks ! ---Barack</tokentext>
<sentencetext>202-456-1111Just dumped my crackberry for a 3GS.
I need to know ASAP.Thanks!---Barack</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570767</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571893</id>
	<title>HAHA...</title>
	<author>Anonymous</author>
	<datestamp>1246637220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>now the manufacturers can patch the vulnerability by sending out a text message to everyone. Gain root access, and do what ever they need to get it fixed. Hopefully the bad guys don't get there first or there could be a bunch of lawsuits waiting at apple's front door.</p></htmltext>
<tokenext>now the manufacturers can patch the vulnerability by sending out a text message to everyone .
Gain root access , and do what ever they need to get it fixed .
Hopefully the bad guys do n't get there first or there could be a bunch of lawsuits waiting at apple 's front door .</tokentext>
<sentencetext>now the manufacturers can patch the vulnerability by sending out a text message to everyone.
Gain root access, and do what ever they need to get it fixed.
Hopefully the bad guys don't get there first or there could be a bunch of lawsuits waiting at apple's front door.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572909</id>
	<title>Re:Well there's your problem!</title>
	<author>0xdeadbeef</author>
	<datestamp>1246643280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>According to wikipedia, its an exension of the SMS standard. I would assume this is where the vulnerabilities lie.</i></p><p>I would assume that you're an ignorant hillbilly who hasn't the slightest clue of what you're talking about, but believes that linking to Wikipedia will get you lots of +1 Informative.</p></htmltext>
<tokenext>According to wikipedia , its an exension of the SMS standard .
I would assume this is where the vulnerabilities lie.I would assume that you 're an ignorant hillbilly who has n't the slightest clue of what you 're talking about , but believes that linking to Wikipedia will get you lots of + 1 Informative .</tokentext>
<sentencetext>According to wikipedia, its an exension of the SMS standard.
I would assume this is where the vulnerabilities lie.I would assume that you're an ignorant hillbilly who hasn't the slightest clue of what you're talking about, but believes that linking to Wikipedia will get you lots of +1 Informative.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571237</id>
	<title>Finally</title>
	<author>Anonymous</author>
	<datestamp>1246633380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Maybe we can work this into a way to cripple IPhone enough so that Apple losses its place as the smartphone market dominate hot chick.  Then Microsoft or Palm can take the spotlight with a pricier less advanced more restrictive replacement with an even more expensive data plan........</p><p>More seriously it will be interesting to see how Apple handles the hacker "attention".  Normally its M$ who has to release patch after patch in the interest of security</p></htmltext>
<tokenext>Maybe we can work this into a way to cripple IPhone enough so that Apple losses its place as the smartphone market dominate hot chick .
Then Microsoft or Palm can take the spotlight with a pricier less advanced more restrictive replacement with an even more expensive data plan........More seriously it will be interesting to see how Apple handles the hacker " attention " .
Normally its M $ who has to release patch after patch in the interest of security</tokentext>
<sentencetext>Maybe we can work this into a way to cripple IPhone enough so that Apple losses its place as the smartphone market dominate hot chick.
Then Microsoft or Palm can take the spotlight with a pricier less advanced more restrictive replacement with an even more expensive data plan........More seriously it will be interesting to see how Apple handles the hacker "attention".
Normally its M$ who has to release patch after patch in the interest of security</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575183</id>
	<title>Re:Cancel Texting</title>
	<author>Thantik</author>
	<datestamp>1246616160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What's funny is that if you say you use email to a teenager, they usually make some snide comment about they use text messaging, email is for old people...<p>

SMS is just email in a more restricted format.  I don't see how people honestly think it's any different. (Ok, yes I do; Most people are sheep.)</p></htmltext>
<tokenext>What 's funny is that if you say you use email to a teenager , they usually make some snide comment about they use text messaging , email is for old people.. . SMS is just email in a more restricted format .
I do n't see how people honestly think it 's any different .
( Ok , yes I do ; Most people are sheep .
)</tokentext>
<sentencetext>What's funny is that if you say you use email to a teenager, they usually make some snide comment about they use text messaging, email is for old people...

SMS is just email in a more restricted format.
I don't see how people honestly think it's any different.
(Ok, yes I do; Most people are sheep.
)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572551</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572441</id>
	<title>Re:Wonder how this goes together ..</title>
	<author>Anonymous</author>
	<datestamp>1246640460000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>http://www.theregister.co.uk/2009/07/02/critical\_iphone\_sms\_bug/</p><p>This is an article that isn't full of the ridiculous hype bullshit that infoworld.com is printing.</p></htmltext>
<tokenext>http : //www.theregister.co.uk/2009/07/02/critical \ _iphone \ _sms \ _bug/This is an article that is n't full of the ridiculous hype bullshit that infoworld.com is printing .</tokentext>
<sentencetext>http://www.theregister.co.uk/2009/07/02/critical\_iphone\_sms\_bug/This is an article that isn't full of the ridiculous hype bullshit that infoworld.com is printing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570727</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572167</id>
	<title>Re:Ouch!</title>
	<author>Anonymous</author>
	<datestamp>1246638720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Remember uuencode/uudecode ?</p></htmltext>
<tokenext>Remember uuencode/uudecode ?</tokentext>
<sentencetext>Remember uuencode/uudecode ?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571489</id>
	<title>Re:Ouch!</title>
	<author>Anonymous</author>
	<datestamp>1246634940000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>This might be linked to the MobileMe Find My iPhone, Remote Wipe, and remote message facilities. If these are commands sent by SMS message from MobileMe, then perhaps they can be overflowed to run arbitrary commands.<br> <br>After all, if you can wipe the phone remotely, then that system has root access, does it not?<br> <br>N.B. I am not a security researcher.</htmltext>
<tokenext>This might be linked to the MobileMe Find My iPhone , Remote Wipe , and remote message facilities .
If these are commands sent by SMS message from MobileMe , then perhaps they can be overflowed to run arbitrary commands .
After all , if you can wipe the phone remotely , then that system has root access , does it not ?
N.B. I am not a security researcher .</tokentext>
<sentencetext>This might be linked to the MobileMe Find My iPhone, Remote Wipe, and remote message facilities.
If these are commands sent by SMS message from MobileMe, then perhaps they can be overflowed to run arbitrary commands.
After all, if you can wipe the phone remotely, then that system has root access, does it not?
N.B. I am not a security researcher.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571097</id>
	<title>But...but...</title>
	<author>Anonymous</author>
	<datestamp>1246632540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"Macs don't get viruses."</p><p>Turns out to be a lie.<nobr> <wbr></nobr>:)</p><p>I'm a pc.</p></htmltext>
<tokenext>" Macs do n't get viruses .
" Turns out to be a lie .
: ) I 'm a pc .</tokentext>
<sentencetext>"Macs don't get viruses.
"Turns out to be a lie.
:)I'm a pc.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571049</id>
	<title>Didn't this just happen?</title>
	<author>Anonymous</author>
	<datestamp>1246632240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How does this compare to the story from <a href="http://it.slashdot.org/article.pl?sid=09/06/16/0017221" title="slashdot.org">two weeks ago?</a> [slashdot.org]</htmltext>
<tokenext>How does this compare to the story from two weeks ago ?
[ slashdot.org ]</tokentext>
<sentencetext>How does this compare to the story from two weeks ago?
[slashdot.org]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571551</id>
	<title>Re:Ouch!</title>
	<author>Sockatume</author>
	<datestamp>1246635360000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>It's not a true SMS-to-root exploit. So far he's only been able to crash part of the device's software with it, he's still looking into whether it can be used to run arbitrary code.</p></htmltext>
<tokenext>It 's not a true SMS-to-root exploit .
So far he 's only been able to crash part of the device 's software with it , he 's still looking into whether it can be used to run arbitrary code .</tokentext>
<sentencetext>It's not a true SMS-to-root exploit.
So far he's only been able to crash part of the device's software with it, he's still looking into whether it can be used to run arbitrary code.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28577895</id>
	<title>no great mystery - police control codes left open</title>
	<author>gregconquest</author>
	<datestamp>1246644720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I don't know why anybody hasn't linked the two together, but SMS control codes are how the police get your phone to send your GPS coordinates when making a 911 call. Control codes are also there for turning the mic on and broadcasting the audio -- and who knows what else? (look up "roaming bug" for more info.)</htmltext>
<tokenext>I do n't know why anybody has n't linked the two together , but SMS control codes are how the police get your phone to send your GPS coordinates when making a 911 call .
Control codes are also there for turning the mic on and broadcasting the audio -- and who knows what else ?
( look up " roaming bug " for more info .
)</tokentext>
<sentencetext>I don't know why anybody hasn't linked the two together, but SMS control codes are how the police get your phone to send your GPS coordinates when making a 911 call.
Control codes are also there for turning the mic on and broadcasting the audio -- and who knows what else?
(look up "roaming bug" for more info.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572551</id>
	<title>Cancel Texting</title>
	<author>joNDoty</author>
	<datestamp>1246641300000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>I recently canceled texting completely on my iPhone 3GS. Texting fees are outrageous and I'm not putting up with them anymore. If you want to text me, send it to my email address. Your phone probably supports texting to an email address and you don't even realize it. You can also reply to free texts I send you and I get notified instantly.</p><p>Sure, I can't receive texts sent to my phone number, but that's a sacrifice I'm willing to make if I'm going to help my country kick this ridiculous habit of overpaying for tiny emails.</p></htmltext>
<tokenext>I recently canceled texting completely on my iPhone 3GS .
Texting fees are outrageous and I 'm not putting up with them anymore .
If you want to text me , send it to my email address .
Your phone probably supports texting to an email address and you do n't even realize it .
You can also reply to free texts I send you and I get notified instantly.Sure , I ca n't receive texts sent to my phone number , but that 's a sacrifice I 'm willing to make if I 'm going to help my country kick this ridiculous habit of overpaying for tiny emails .</tokentext>
<sentencetext>I recently canceled texting completely on my iPhone 3GS.
Texting fees are outrageous and I'm not putting up with them anymore.
If you want to text me, send it to my email address.
Your phone probably supports texting to an email address and you don't even realize it.
You can also reply to free texts I send you and I get notified instantly.Sure, I can't receive texts sent to my phone number, but that's a sacrifice I'm willing to make if I'm going to help my country kick this ridiculous habit of overpaying for tiny emails.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005</id>
	<title>SMS limit isn't 140 characters</title>
	<author>praseodym</author>
	<datestamp>1246632000000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>SMS has a limit of 160 characters, not 140. Twitter has a 140-character limit because of its SMS-interface which leaves 20 characters for commands etc. in addition to the message.</p></htmltext>
<tokenext>SMS has a limit of 160 characters , not 140 .
Twitter has a 140-character limit because of its SMS-interface which leaves 20 characters for commands etc .
in addition to the message .</tokentext>
<sentencetext>SMS has a limit of 160 characters, not 140.
Twitter has a 140-character limit because of its SMS-interface which leaves 20 characters for commands etc.
in addition to the message.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571725</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>Anonymous</author>
	<datestamp>1246636260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>if you read the other article cited you would have seen "The SMS vulnerability allows an attacker to run software code on the phone that is sent by SMS over a mobile operator's network."</p><p>get off your high horse d-bag</p></htmltext>
<tokenext>if you read the other article cited you would have seen " The SMS vulnerability allows an attacker to run software code on the phone that is sent by SMS over a mobile operator 's network .
" get off your high horse d-bag</tokentext>
<sentencetext>if you read the other article cited you would have seen "The SMS vulnerability allows an attacker to run software code on the phone that is sent by SMS over a mobile operator's network.
"get off your high horse d-bag</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571079</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570787</id>
	<title>I, for one, would like to say...</title>
	<author>Anonymous</author>
	<datestamp>1246630380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>DERRRRRRRRRRRRRRRRHHHH!!!!!

Steve Jobs derrhrhhhhhhhhhhhhhh.</htmltext>
<tokenext>DERRRRRRRRRRRRRRRRHHHH ! ! ! ! !
Steve Jobs derrhrhhhhhhhhhhhhhh .</tokentext>
<sentencetext>DERRRRRRRRRRRRRRRRHHHH!!!!!
Steve Jobs derrhrhhhhhhhhhhhhhh.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570919</id>
	<title>Re:Ouch!</title>
	<author>dna\_(c)(tm)(r)</author>
	<datestamp>1246631400000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext>The only plausible explanation is that Microsoft must have bought Apple...</htmltext>
<tokenext>The only plausible explanation is that Microsoft must have bought Apple.. .</tokentext>
<sentencetext>The only plausible explanation is that Microsoft must have bought Apple...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571353</id>
	<title>Re:Ouch!</title>
	<author>forand</author>
	<datestamp>1246634220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>My best guess would be the cell providers. They want someway to control the devices on their network or update them remotely if so needed.</htmltext>
<tokenext>My best guess would be the cell providers .
They want someway to control the devices on their network or update them remotely if so needed .</tokentext>
<sentencetext>My best guess would be the cell providers.
They want someway to control the devices on their network or update them remotely if so needed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574001</id>
	<title>Re:Wonder how this goes together ..</title>
	<author>Hurricane78</author>
	<datestamp>1246650540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Man I just found someone else openly describing the way to root an iPhone via SMS. (I don't know if he started to search after he heard this or what.)</p><p>I HAVE to try this on some dudes (and I girl) I know.</p><p>Then I will make a lolappleboi photo of them, and caption it with "Laem iPwn oozr iz laem." (Think of the original meaning of "lame".)<br>Or, depending on what happens, I could use just one word: "iBurn".<nobr> <wbr></nobr>:D</p><p>Ok, I know I'm evil.<nobr> <wbr></nobr>:D</p></htmltext>
<tokenext>Man I just found someone else openly describing the way to root an iPhone via SMS .
( I do n't know if he started to search after he heard this or what .
) I HAVE to try this on some dudes ( and I girl ) I know.Then I will make a lolappleboi photo of them , and caption it with " Laem iPwn oozr iz laem .
" ( Think of the original meaning of " lame " .
) Or , depending on what happens , I could use just one word : " iBurn " .
: DOk , I know I 'm evil .
: D</tokentext>
<sentencetext>Man I just found someone else openly describing the way to root an iPhone via SMS.
(I don't know if he started to search after he heard this or what.
)I HAVE to try this on some dudes (and I girl) I know.Then I will make a lolappleboi photo of them, and caption it with "Laem iPwn oozr iz laem.
" (Think of the original meaning of "lame".
)Or, depending on what happens, I could use just one word: "iBurn".
:DOk, I know I'm evil.
:D</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570727</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572409</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>Dragonslicer</author>
	<datestamp>1246640280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Ummm, carriers stand to profit from this so why would they?</p></div><p>Maybe I'm not thinking evilly enough, but how would a carrier profit from phones on their network being exploited? If anything, it would start costing them resources when the phones are used to launch DDoS attacks.</p></div>
	</htmltext>
<tokenext>Ummm , carriers stand to profit from this so why would they ? Maybe I 'm not thinking evilly enough , but how would a carrier profit from phones on their network being exploited ?
If anything , it would start costing them resources when the phones are used to launch DDoS attacks .</tokentext>
<sentencetext>Ummm, carriers stand to profit from this so why would they?Maybe I'm not thinking evilly enough, but how would a carrier profit from phones on their network being exploited?
If anything, it would start costing them resources when the phones are used to launch DDoS attacks.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570917</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570867</id>
	<title>SMS?</title>
	<author>yourassOA</author>
	<datestamp>1246631040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext>Seems more like a back door than anything and now that it has been discovered Apple will try to fix (hide it better) the problem. Seems to me like most of the vulnerabilities would benefit law enforcement the most, weird huh? It not like this never happened with Microsoft, encryption key, and the FBI.</htmltext>
<tokenext>Seems more like a back door than anything and now that it has been discovered Apple will try to fix ( hide it better ) the problem .
Seems to me like most of the vulnerabilities would benefit law enforcement the most , weird huh ?
It not like this never happened with Microsoft , encryption key , and the FBI .</tokentext>
<sentencetext>Seems more like a back door than anything and now that it has been discovered Apple will try to fix (hide it better) the problem.
Seems to me like most of the vulnerabilities would benefit law enforcement the most, weird huh?
It not like this never happened with Microsoft, encryption key, and the FBI.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571813</id>
	<title>Re:Seems to affect other smart phones as well ...</title>
	<author>El\_Muerte\_TDS</author>
	<datestamp>1246636680000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>No learn to read. The second link says that they have technology to send an SMS Message to a phone without needing a carrier. It doesn't say anything about exploiting bugs in the handling of the SMS Message.</p></htmltext>
<tokenext>No learn to read .
The second link says that they have technology to send an SMS Message to a phone without needing a carrier .
It does n't say anything about exploiting bugs in the handling of the SMS Message .</tokentext>
<sentencetext>No learn to read.
The second link says that they have technology to send an SMS Message to a phone without needing a carrier.
It doesn't say anything about exploiting bugs in the handling of the SMS Message.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571067</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570753</id>
	<title>So I assume a buffer overflow?</title>
	<author>Anonymous</author>
	<datestamp>1246630200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Wow, buffer overflows in 2009.</p><p>I guess ARM needs to implement No Execute Bit in their CPUs. You can't protect against dumb programmers.</p><p>If it wasn't a buffer overflow, then how in the name of all that is chocolate did some binary data get to be executable?!</p><p>--<br>Slashdot requires you to wait between each successful posting of a comment to allow everyone a fair chance at posting a comment.<br>It's been 13 minutes since you last successfully posted a comment</p><p>LOL.</p></htmltext>
<tokenext>Wow , buffer overflows in 2009.I guess ARM needs to implement No Execute Bit in their CPUs .
You ca n't protect against dumb programmers.If it was n't a buffer overflow , then how in the name of all that is chocolate did some binary data get to be executable ?
! --Slashdot requires you to wait between each successful posting of a comment to allow everyone a fair chance at posting a comment.It 's been 13 minutes since you last successfully posted a commentLOL .</tokentext>
<sentencetext>Wow, buffer overflows in 2009.I guess ARM needs to implement No Execute Bit in their CPUs.
You can't protect against dumb programmers.If it wasn't a buffer overflow, then how in the name of all that is chocolate did some binary data get to be executable?
!--Slashdot requires you to wait between each successful posting of a comment to allow everyone a fair chance at posting a comment.It's been 13 minutes since you last successfully posted a commentLOL.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572471</id>
	<title>Re:Ouch!</title>
	<author>Enzo1977</author>
	<datestamp>1246640700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>the same people who insisted on having true MMS on the iPhone, although e-mail has always been a perfectly functionable alternative.</p></htmltext>
<tokenext>the same people who insisted on having true MMS on the iPhone , although e-mail has always been a perfectly functionable alternative .</tokentext>
<sentencetext>the same people who insisted on having true MMS on the iPhone, although e-mail has always been a perfectly functionable alternative.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28576759</id>
	<title>Re:At least SOMEBODY has full access to my iPhone!</title>
	<author>slimjim8094</author>
	<datestamp>1246630380000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext><p>Just jailbreak the fucking thing like the rest of us and quit bitching. I just finished a SSH session to my phone (where I su to root).</p><p>I consider that owning my phone, especially because it's even relatively safe to unlock then. Everybody who isn't willing to do that, please just shut up. Apple doesn't seem to care too much about the jailbreak; it works out great. "Normal" users don't get confused, and everybody else can run multiple apps, get SSH, turn-by-turn directions, etc.</p><p>Seriously, take the 5 minutes and do it. You'll thank me. Or stop complaining.</p></htmltext>
<tokenext>Just jailbreak the fucking thing like the rest of us and quit bitching .
I just finished a SSH session to my phone ( where I su to root ) .I consider that owning my phone , especially because it 's even relatively safe to unlock then .
Everybody who is n't willing to do that , please just shut up .
Apple does n't seem to care too much about the jailbreak ; it works out great .
" Normal " users do n't get confused , and everybody else can run multiple apps , get SSH , turn-by-turn directions , etc.Seriously , take the 5 minutes and do it .
You 'll thank me .
Or stop complaining .</tokentext>
<sentencetext>Just jailbreak the fucking thing like the rest of us and quit bitching.
I just finished a SSH session to my phone (where I su to root).I consider that owning my phone, especially because it's even relatively safe to unlock then.
Everybody who isn't willing to do that, please just shut up.
Apple doesn't seem to care too much about the jailbreak; it works out great.
"Normal" users don't get confused, and everybody else can run multiple apps, get SSH, turn-by-turn directions, etc.Seriously, take the 5 minutes and do it.
You'll thank me.
Or stop complaining.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570957</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571953</id>
	<title>Are you proposing an SMS evil bit?</title>
	<author>Anonymous</author>
	<datestamp>1246637520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>it seems like any carrier of the iPhone should want to implement a simple filter to remove any malicious SMSs from the system</p></div></blockquote><p>This is a serious sentence?</p></div>
	</htmltext>
<tokenext>it seems like any carrier of the iPhone should want to implement a simple filter to remove any malicious SMSs from the systemThis is a serious sentence ?</tokentext>
<sentencetext>it seems like any carrier of the iPhone should want to implement a simple filter to remove any malicious SMSs from the systemThis is a serious sentence?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570983</id>
	<title>Re:Well there's your problem!</title>
	<author>Anonymous</author>
	<datestamp>1246631880000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>Yeah! Ban the characters '0' and '1' from text messages and stop this binary nonsense!</htmltext>
<tokenext>Yeah !
Ban the characters '0 ' and '1 ' from text messages and stop this binary nonsense !</tokentext>
<sentencetext>Yeah!
Ban the characters '0' and '1' from text messages and stop this binary nonsense!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573141</id>
	<title>Re:Ouch!</title>
	<author>BikeHelmet</author>
	<datestamp>1246644840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Indeed. Vulnerability, or backdoor? "Fixing" the solution probably involves verifying the text message came from Apple.</p></htmltext>
<tokenext>Indeed .
Vulnerability , or backdoor ?
" Fixing " the solution probably involves verifying the text message came from Apple .</tokentext>
<sentencetext>Indeed.
Vulnerability, or backdoor?
"Fixing" the solution probably involves verifying the text message came from Apple.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570727</id>
	<title>Wonder how this goes together ..</title>
	<author>Anonymous</author>
	<datestamp>1246630080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Wondering if this can be combined with iPhone's ability to heat red hot while in your pocket</p></htmltext>
<tokenext>Wondering if this can be combined with iPhone 's ability to heat red hot while in your pocket</tokentext>
<sentencetext>Wondering if this can be combined with iPhone's ability to heat red hot while in your pocket</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574583</id>
	<title>Re:i sense a disturbence in the force</title>
	<author>ae1294</author>
	<datestamp>1246611900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>about garage band and iphoto..</p></div><p>I thought you wrote ipotato.... I was getting all excited about a new Apple Product and shit...</p></div>
	</htmltext>
<tokenext>about garage band and iphoto..I thought you wrote ipotato.... I was getting all excited about a new Apple Product and shit.. .</tokentext>
<sentencetext>about garage band and iphoto..I thought you wrote ipotato.... I was getting all excited about a new Apple Product and shit...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571217</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574033</id>
	<title>Re:i sense a disturbence in the force</title>
	<author>Hurricane78</author>
	<datestamp>1246650780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>...because their iPwnes now cry for them. All day and all night. About Vi4gra, P3nis enlagrements, Xial1s, and in russian about DDOSing the iTunes store.</p></htmltext>
<tokenext>...because their iPwnes now cry for them .
All day and all night .
About Vi4gra , P3nis enlagrements , Xial1s , and in russian about DDOSing the iTunes store .</tokentext>
<sentencetext>...because their iPwnes now cry for them.
All day and all night.
About Vi4gra, P3nis enlagrements, Xial1s, and in russian about DDOSing the iTunes store.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570837</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570917</id>
	<title>Re:Can't Carriers Stop this?</title>
	<author>Anonymous</author>
	<datestamp>1246631400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Ummm, carriers stand to profit from this so why would they?</htmltext>
<tokenext>Ummm , carriers stand to profit from this so why would they ?</tokentext>
<sentencetext>Ummm, carriers stand to profit from this so why would they?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571067</id>
	<title>Seems to affect other smart phones as well ...</title>
	<author>Anonymous</author>
	<datestamp>1246632360000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>from the second link: "We present techniques which allow a researcher to inject SMS messages into iPhone, Android, and Windows Mobile devices."</htmltext>
<tokenext>from the second link : " We present techniques which allow a researcher to inject SMS messages into iPhone , Android , and Windows Mobile devices .
"</tokentext>
<sentencetext>from the second link: "We present techniques which allow a researcher to inject SMS messages into iPhone, Android, and Windows Mobile devices.
"</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572401
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572471
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571495
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574583
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571217
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570837
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572909
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572193
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570767
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574033
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570837
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573483
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570959
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570767
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572441
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570727
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573733
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572587
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574001
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570727
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571953
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28576759
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570957
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575183
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572551
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572161
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570919
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573521
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572059
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571645
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573571
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571813
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571067
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573141
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571705
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571067
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571247
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571725
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571079
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571393
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572409
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570917
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571057
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572863
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571413
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571365
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574623
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571303
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570901
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575005
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571353
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575293
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570841
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571079
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571551
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571637
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1210222_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570983
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570867
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570837
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574033
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571217
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574583
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572551
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575183
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570743
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570799
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570685
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571049
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570841
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575293
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570957
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28576759
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573355
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570815
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571413
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572161
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571411
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572909
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571247
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570983
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571057
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572059
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572863
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570739
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571365
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571953
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573733
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571079
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571725
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574847
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573571
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570917
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572409
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571097
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570767
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572193
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570959
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571005
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572587
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571637
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571645
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571303
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574623
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571067
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574063
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571813
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570727
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572441
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28574001
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1210222.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570693
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571551
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570847
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573521
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571705
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572401
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572167
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571353
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571489
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570919
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571495
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28571393
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28575005
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28572471
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573141
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28573483
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1210222.28570901
</commentlist>
</conversation>
