<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_01_19_0147239</id>
	<title>D-Link Warns of Vulnerable Routers</title>
	<author>kdawson</author>
	<datestamp>1263912780000</datestamp>
	<htmltext>wiedzmin sends in news of a <a href="http://www.computerworld.com/s/article/9145139/D\_Link\_issues\_fixes\_for\_router\_vulnerabilities?taxonomyId=80">vulnerability in some D-Link home routers</a>. The company has made new firmware available for download. <i>"D-Link announced today that the problem, discovered by security researchers SourceSec, affects three of its wireless routers: DIR-855 (hardware version A2), DIR-655 (versions A1 to A4), and DIR-635 (version B). The problem lies in D-Link's implementation of Cisco's Home Network Administration Protocol, which allows remote router configuration. The scope of the vulnerability is greatly reduced by the fact that these router models were not shipped with the affected firmware by default, so only customers who updated their firmware are potentially affected. Or at least this was indicated in the company's response to the SourceSac claim that all D-Link routers sold since 2006 were affected."</i> SourceSec apparently <a href="http://www.sourcesec.com/2010/01/09/d-link-routers-one-hack-to-own-them-all/">made their research available</a>, including an exploitation tool, without ever contacting D-Link.</htmltext>
<tokenext>wiedzmin sends in news of a vulnerability in some D-Link home routers .
The company has made new firmware available for download .
" D-Link announced today that the problem , discovered by security researchers SourceSec , affects three of its wireless routers : DIR-855 ( hardware version A2 ) , DIR-655 ( versions A1 to A4 ) , and DIR-635 ( version B ) .
The problem lies in D-Link 's implementation of Cisco 's Home Network Administration Protocol , which allows remote router configuration .
The scope of the vulnerability is greatly reduced by the fact that these router models were not shipped with the affected firmware by default , so only customers who updated their firmware are potentially affected .
Or at least this was indicated in the company 's response to the SourceSac claim that all D-Link routers sold since 2006 were affected .
" SourceSec apparently made their research available , including an exploitation tool , without ever contacting D-Link .</tokentext>
<sentencetext>wiedzmin sends in news of a vulnerability in some D-Link home routers.
The company has made new firmware available for download.
"D-Link announced today that the problem, discovered by security researchers SourceSec, affects three of its wireless routers: DIR-855 (hardware version A2), DIR-655 (versions A1 to A4), and DIR-635 (version B).
The problem lies in D-Link's implementation of Cisco's Home Network Administration Protocol, which allows remote router configuration.
The scope of the vulnerability is greatly reduced by the fact that these router models were not shipped with the affected firmware by default, so only customers who updated their firmware are potentially affected.
Or at least this was indicated in the company's response to the SourceSac claim that all D-Link routers sold since 2006 were affected.
" SourceSec apparently made their research available, including an exploitation tool, without ever contacting D-Link.</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30818652</id>
	<title>Dlink-feh</title>
	<author>Anonymous</author>
	<datestamp>1263913560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I wouldn't buy a BRICK from DLink anymore.  I have yet to see anything made by them that wasn't the worst I'd ever seen of whatever it was.  NICs, routers, switches, whatever, they were all crap, with crap drivers, crap firmware, crap everything.  They must have the schmoozingest marketing department ever to still be in business.</p></htmltext>
<tokenext>I would n't buy a BRICK from DLink anymore .
I have yet to see anything made by them that was n't the worst I 'd ever seen of whatever it was .
NICs , routers , switches , whatever , they were all crap , with crap drivers , crap firmware , crap everything .
They must have the schmoozingest marketing department ever to still be in business .</tokentext>
<sentencetext>I wouldn't buy a BRICK from DLink anymore.
I have yet to see anything made by them that wasn't the worst I'd ever seen of whatever it was.
NICs, routers, switches, whatever, they were all crap, with crap drivers, crap firmware, crap everything.
They must have the schmoozingest marketing department ever to still be in business.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816156</id>
	<title>Re:Just checked D-Link's website</title>
	<author>crispytwo</author>
	<datestamp>1263836520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Whatever you do, don't install v1.32NA. It's garbage! I wish I never did!</p><p>I've been waiting for an update for months now, with a reboot every couple of days.<br>When it works, it's fine, but it is not certainly not stable.</p></htmltext>
<tokenext>Whatever you do , do n't install v1.32NA .
It 's garbage !
I wish I never did ! I 've been waiting for an update for months now , with a reboot every couple of days.When it works , it 's fine , but it is not certainly not stable .</tokentext>
<sentencetext>Whatever you do, don't install v1.32NA.
It's garbage!
I wish I never did!I've been waiting for an update for months now, with a reboot every couple of days.When it works, it's fine, but it is not certainly not stable.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815978</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30819444</id>
	<title>Re:DGL-4500 users left screwed</title>
	<author>GameboyRMH</author>
	<datestamp>1263917880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's odd that these days the top-of-the-line, most expensive flagship products are the most buggy. See:</p><p>- MSI X58 Eclipse SLI (BIOS reflash bricking problem, some problems with the IOH (northbridge) thermal compound application from the factory, and it's not their first board to have this)</p><p>- Nokia N900 (hardware flaws including the USB port coming clean off the board in normal use, a fuckton of bugs in original OS release).</p><p>- There's a similar clusterfuck with a high-end Linksys router (can't remember the model, high-end "gaming" unit with two separate wireless adapters).</p><p>- All Logitech PC gamepads (including some very costly cordless models): the potentiometers wear out after a few months. Some people reported them faulty right out of the box. Logitech has entirely ignored the issue and continued selling these products.</p><p>- The Intel SSD clusterfuck (rapid performance degradation, drives bricked during reflash, total data loss, etc).</p><p>- "self-bricking" WD and Seagate terabyte drives (from what I hear they weren't truly bricked, and could be fixed with a reflash)</p><p>Not just electronics, cars too:</p><p>- Early Mazda RX8s had engines that would eat themselves.</p><p>- The Toyota MR-S has oil starvation problems in hard cornering, which is kind of like a motorcycle having oil starvation problems in hard acceleration.</p><p>- Early Honda S2000s had a suspension setup better suited to a skilled driver intent on track use than the other 99\% of the owners (guess what happened).</p><p>- The Evo 10 initially had shitty ECU code that caused it to guzzle gas and run like crap, and a plastic e-throttle pedal that would break clean off if you were unlucky.</p><p>- Don't forget the Lexus luxury cars where the ECU thinks the e-throttle is floored (I think they tried to pass off some excuse about floor mats?).</p><p>- The Caparo T1, a <b>half-million dollar</b> breakdown machine that's also had problems with the e-throttle sticking open. Luckily there are ignition and battery cutoffs on the dash.</p></htmltext>
<tokenext>It 's odd that these days the top-of-the-line , most expensive flagship products are the most buggy .
See : - MSI X58 Eclipse SLI ( BIOS reflash bricking problem , some problems with the IOH ( northbridge ) thermal compound application from the factory , and it 's not their first board to have this ) - Nokia N900 ( hardware flaws including the USB port coming clean off the board in normal use , a fuckton of bugs in original OS release ) .- There 's a similar clusterfuck with a high-end Linksys router ( ca n't remember the model , high-end " gaming " unit with two separate wireless adapters ) .- All Logitech PC gamepads ( including some very costly cordless models ) : the potentiometers wear out after a few months .
Some people reported them faulty right out of the box .
Logitech has entirely ignored the issue and continued selling these products.- The Intel SSD clusterfuck ( rapid performance degradation , drives bricked during reflash , total data loss , etc ) .- " self-bricking " WD and Seagate terabyte drives ( from what I hear they were n't truly bricked , and could be fixed with a reflash ) Not just electronics , cars too : - Early Mazda RX8s had engines that would eat themselves.- The Toyota MR-S has oil starvation problems in hard cornering , which is kind of like a motorcycle having oil starvation problems in hard acceleration.- Early Honda S2000s had a suspension setup better suited to a skilled driver intent on track use than the other 99 \ % of the owners ( guess what happened ) .- The Evo 10 initially had shitty ECU code that caused it to guzzle gas and run like crap , and a plastic e-throttle pedal that would break clean off if you were unlucky.- Do n't forget the Lexus luxury cars where the ECU thinks the e-throttle is floored ( I think they tried to pass off some excuse about floor mats ?
) .- The Caparo T1 , a half-million dollar breakdown machine that 's also had problems with the e-throttle sticking open .
Luckily there are ignition and battery cutoffs on the dash .</tokentext>
<sentencetext>It's odd that these days the top-of-the-line, most expensive flagship products are the most buggy.
See:- MSI X58 Eclipse SLI (BIOS reflash bricking problem, some problems with the IOH (northbridge) thermal compound application from the factory, and it's not their first board to have this)- Nokia N900 (hardware flaws including the USB port coming clean off the board in normal use, a fuckton of bugs in original OS release).- There's a similar clusterfuck with a high-end Linksys router (can't remember the model, high-end "gaming" unit with two separate wireless adapters).- All Logitech PC gamepads (including some very costly cordless models): the potentiometers wear out after a few months.
Some people reported them faulty right out of the box.
Logitech has entirely ignored the issue and continued selling these products.- The Intel SSD clusterfuck (rapid performance degradation, drives bricked during reflash, total data loss, etc).- "self-bricking" WD and Seagate terabyte drives (from what I hear they weren't truly bricked, and could be fixed with a reflash)Not just electronics, cars too:- Early Mazda RX8s had engines that would eat themselves.- The Toyota MR-S has oil starvation problems in hard cornering, which is kind of like a motorcycle having oil starvation problems in hard acceleration.- Early Honda S2000s had a suspension setup better suited to a skilled driver intent on track use than the other 99\% of the owners (guess what happened).- The Evo 10 initially had shitty ECU code that caused it to guzzle gas and run like crap, and a plastic e-throttle pedal that would break clean off if you were unlucky.- Don't forget the Lexus luxury cars where the ECU thinks the e-throttle is floored (I think they tried to pass off some excuse about floor mats?
).- The Caparo T1, a half-million dollar breakdown machine that's also had problems with the e-throttle sticking open.
Luckily there are ignition and battery cutoffs on the dash.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817782</id>
	<title>Re:Attack is Significant but Will not be Pandemic</title>
	<author>Carewolf</author>
	<datestamp>1263903300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I can't say for all the affected routers but the D-Link 655 has a guest mode for unsecured wireless networks. This means this essid only provides internet and not access to the LAN. To get to the LAN you need to use the other secure essid (the router can handle multiple wireless networks with varying security).</p></htmltext>
<tokenext>I ca n't say for all the affected routers but the D-Link 655 has a guest mode for unsecured wireless networks .
This means this essid only provides internet and not access to the LAN .
To get to the LAN you need to use the other secure essid ( the router can handle multiple wireless networks with varying security ) .</tokentext>
<sentencetext>I can't say for all the affected routers but the D-Link 655 has a guest mode for unsecured wireless networks.
This means this essid only provides internet and not access to the LAN.
To get to the LAN you need to use the other secure essid (the router can handle multiple wireless networks with varying security).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815988</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815846</id>
	<title>Attack is Significant but Will not be Pandemic</title>
	<author>Anonymous</author>
	<datestamp>1263832620000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>This attack only works when a system on the LAN initiates it.</p><p>It is possible to get a system on the lan to initiate it with a DNS rebinding attack and javascript on a malicious web page, but that is far from a trivial attack.</p><p>I'm guessing that this is successfully used only in highly targeted attacks.</p></htmltext>
<tokenext>This attack only works when a system on the LAN initiates it.It is possible to get a system on the lan to initiate it with a DNS rebinding attack and javascript on a malicious web page , but that is far from a trivial attack.I 'm guessing that this is successfully used only in highly targeted attacks .</tokentext>
<sentencetext>This attack only works when a system on the LAN initiates it.It is possible to get a system on the lan to initiate it with a DNS rebinding attack and javascript on a malicious web page, but that is far from a trivial attack.I'm guessing that this is successfully used only in highly targeted attacks.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815686</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>h4rr4r</author>
	<datestamp>1263831060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>All that would have earned them is a lawsuit. Plus Dlink would never have fixed it.</p></htmltext>
<tokenext>All that would have earned them is a lawsuit .
Plus Dlink would never have fixed it .</tokentext>
<sentencetext>All that would have earned them is a lawsuit.
Plus Dlink would never have fixed it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817036</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Carewolf</author>
	<datestamp>1263892500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I see a beta version 1.31EUb02 listed from the 18/1 with the specific changelog of fixing this vulnerability.</p></htmltext>
<tokenext>I see a beta version 1.31EUb02 listed from the 18/1 with the specific changelog of fixing this vulnerability .</tokentext>
<sentencetext>I see a beta version 1.31EUb02 listed from the 18/1 with the specific changelog of fixing this vulnerability.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816856</id>
	<title>Re:fdsfds</title>
	<author>Hitokiri Battousai</author>
	<datestamp>1263933540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>He didn't even fgsfds right...</htmltext>
<tokenext>He did n't even fgsfds right.. .</tokentext>
<sentencetext>He didn't even fgsfds right...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815630</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815924</id>
	<title>Re:fdsfds</title>
	<author>Runaway1956</author>
	<datestamp>1263833460000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Real men (not to mention wannabes and dykes) prefer real boots - not fake fur gay shit.</p><p><a href="http://www.wolverine.com/US/Gallery/N/WORK.aspx" title="wolverine.com" rel="nofollow">http://www.wolverine.com/US/Gallery/N/WORK.aspx</a> [wolverine.com]</p><p>Take your homoerotic crap elsewhere.</p></htmltext>
<tokenext>Real men ( not to mention wannabes and dykes ) prefer real boots - not fake fur gay shit.http : //www.wolverine.com/US/Gallery/N/WORK.aspx [ wolverine.com ] Take your homoerotic crap elsewhere .</tokentext>
<sentencetext>Real men (not to mention wannabes and dykes) prefer real boots - not fake fur gay shit.http://www.wolverine.com/US/Gallery/N/WORK.aspx [wolverine.com]Take your homoerotic crap elsewhere.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815630</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815914</id>
	<title>huh</title>
	<author>Anonymous</author>
	<datestamp>1263833280000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>well call me a faggot nigger!</p></htmltext>
<tokenext>well call me a faggot nigger !</tokentext>
<sentencetext>well call me a faggot nigger!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30819190</id>
	<title>D-Link...</title>
	<author>Anonymous</author>
	<datestamp>1263916620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>D-Link goes ape-shit about home router, really ?</p><p>How about freaking professional ISP Access Switches DES-3028, which love to turn themselves into hubs with high probability ?</p><p>http://forum.dlink.ru/viewtopic.php?t=96443<br>http://forum.nag.ru/forum/index.php?showtopic=52882<br>http://nag.ru/news/15587/<br>(in russian, use google-translate if must)</p><p>instead of learning MACs(48 bit) and VIDs(12 bit) its Broadcom board uses weak 13 bit hash of partial MAC+VID...<br>guess what happens when its own hash match client's one or several or other switch...</p><p>does D-Link, Zyxel and other vendors, who use same board, care about those ?</p><p>I know, i know, only russian niggards use them, but DIRs and DGSs is what usually on the other side...</p></htmltext>
<tokenext>D-Link goes ape-shit about home router , really ? How about freaking professional ISP Access Switches DES-3028 , which love to turn themselves into hubs with high probability ? http : //forum.dlink.ru/viewtopic.php ? t = 96443http : //forum.nag.ru/forum/index.php ? showtopic = 52882http : //nag.ru/news/15587/ ( in russian , use google-translate if must ) instead of learning MACs ( 48 bit ) and VIDs ( 12 bit ) its Broadcom board uses weak 13 bit hash of partial MAC + VID...guess what happens when its own hash match client 's one or several or other switch...does D-Link , Zyxel and other vendors , who use same board , care about those ? I know , i know , only russian niggards use them , but DIRs and DGSs is what usually on the other side.. .</tokentext>
<sentencetext>D-Link goes ape-shit about home router, really ?How about freaking professional ISP Access Switches DES-3028, which love to turn themselves into hubs with high probability ?http://forum.dlink.ru/viewtopic.php?t=96443http://forum.nag.ru/forum/index.php?showtopic=52882http://nag.ru/news/15587/(in russian, use google-translate if must)instead of learning MACs(48 bit) and VIDs(12 bit) its Broadcom board uses weak 13 bit hash of partial MAC+VID...guess what happens when its own hash match client's one or several or other switch...does D-Link, Zyxel and other vendors, who use same board, care about those ?I know, i know, only russian niggards use them, but DIRs and DGSs is what usually on the other side...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786</id>
	<title>DGL-4500 users left screwed</title>
	<author>Anonymous</author>
	<datestamp>1263832140000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>If anyone has a DGL-4500 router, and experiences constant lockups with it (forced to power cycle the unit); your not alone. Apparently, there is a bug with DNS forwarding that started with firmware rev 1.21. It's been since July 2009, and the best you can hope for is an update still in beta. We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.</p><p>As it stands, users of this model are furious. Some are threatening a class-action lawsuit against them. By all means, please read through the D-Link forum before you think about buying one of their products.<br><a href="http://forums.dlink.com/index.php?board=144.0" title="dlink.com">http://forums.dlink.com/index.php?board=144.0</a> [dlink.com]</p></htmltext>
<tokenext>If anyone has a DGL-4500 router , and experiences constant lockups with it ( forced to power cycle the unit ) ; your not alone .
Apparently , there is a bug with DNS forwarding that started with firmware rev 1.21 .
It 's been since July 2009 , and the best you can hope for is an update still in beta .
We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.As it stands , users of this model are furious .
Some are threatening a class-action lawsuit against them .
By all means , please read through the D-Link forum before you think about buying one of their products.http : //forums.dlink.com/index.php ? board = 144.0 [ dlink.com ]</tokentext>
<sentencetext>If anyone has a DGL-4500 router, and experiences constant lockups with it (forced to power cycle the unit); your not alone.
Apparently, there is a bug with DNS forwarding that started with firmware rev 1.21.
It's been since July 2009, and the best you can hope for is an update still in beta.
We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.As it stands, users of this model are furious.
Some are threatening a class-action lawsuit against them.
By all means, please read through the D-Link forum before you think about buying one of their products.http://forums.dlink.com/index.php?board=144.0 [dlink.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30868038</id>
	<title>Contact with D-Link only for Windows users</title>
	<author>Anonymous</author>
	<datestamp>1264240320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>To get in touch with D-Link you cannot write a email (at least not for Swedish D-Link) or fill in a web form, you have to install a plug-in to your internet explorer 6 or 7 . Thus I have my last D-Link product purchased! D-Link if from now banned on my network!<nobr> <wbr></nobr>// Linux on all computers at home!</p></htmltext>
<tokenext>To get in touch with D-Link you can not write a email ( at least not for Swedish D-Link ) or fill in a web form , you have to install a plug-in to your internet explorer 6 or 7 .
Thus I have my last D-Link product purchased !
D-Link if from now banned on my network !
// Linux on all computers at home !</tokentext>
<sentencetext>To get in touch with D-Link you cannot write a email (at least not for Swedish D-Link) or fill in a web form, you have to install a plug-in to your internet explorer 6 or 7 .
Thus I have my last D-Link product purchased!
D-Link if from now banned on my network!
// Linux on all computers at home!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815708</id>
	<title>Sky is falling! ...I think, maybe.</title>
	<author>djupedal</author>
	<datestamp>1263831300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>&gt;"<i>The scope of the vulnerability is greatly reduced by the fact that these router models were not shipped with the affected firmware by default, so only customers who updated their firmware are potentially affected. Or at least this was indicated in the company's response to the SourceSac claim that all D-Link routers sold since 2006 were affected."</i>
<br>
<br>
It's one thing to be a commenter/whistle-blower - it is entirely another to be an apologist in the same breath.
<br>
<br>
Once you pull the trigger, you can't run, catch the bullet and put it back in the same chamber, eh? A simple <i>"only customers who updated their firmware are potentially affected"</i> would have been fine...if only you'd left it there<nobr> <wbr></nobr>:)
<br>
<br>
We'll let it go this time, but do it again and it's gonna be all 'look people! point and laugh! point and laugh!!!!</htmltext>
<tokenext>&gt; " The scope of the vulnerability is greatly reduced by the fact that these router models were not shipped with the affected firmware by default , so only customers who updated their firmware are potentially affected .
Or at least this was indicated in the company 's response to the SourceSac claim that all D-Link routers sold since 2006 were affected .
" It 's one thing to be a commenter/whistle-blower - it is entirely another to be an apologist in the same breath .
Once you pull the trigger , you ca n't run , catch the bullet and put it back in the same chamber , eh ?
A simple " only customers who updated their firmware are potentially affected " would have been fine...if only you 'd left it there : ) We 'll let it go this time , but do it again and it 's gon na be all 'look people !
point and laugh !
point and laugh ! ! !
!</tokentext>
<sentencetext>&gt;"The scope of the vulnerability is greatly reduced by the fact that these router models were not shipped with the affected firmware by default, so only customers who updated their firmware are potentially affected.
Or at least this was indicated in the company's response to the SourceSac claim that all D-Link routers sold since 2006 were affected.
"


It's one thing to be a commenter/whistle-blower - it is entirely another to be an apologist in the same breath.
Once you pull the trigger, you can't run, catch the bullet and put it back in the same chamber, eh?
A simple "only customers who updated their firmware are potentially affected" would have been fine...if only you'd left it there :)


We'll let it go this time, but do it again and it's gonna be all 'look people!
point and laugh!
point and laugh!!!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816134</id>
	<title>Don't make me upgrade to 1.3x!</title>
	<author>ender-</author>
	<datestamp>1263836280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's the latest I see too.</p><p>My concern with the DIR-655 is that I'm still at v1.21 [HW rev A3]. I've read nothing but nightmare stories of people with perfectly stable 1.2x routers who then upgraded to 1.3X firmwares and had tons of trouble and instability. At v1.21 my router is absolutely rock solid. This is the best, most stable wireless router I've ever had.  If the 1.21 firmware is affected, and I'm forced to upgrade to 1.3X and it causes my router to become unstable, I'm going to be PISSED!</p><p>I realize I might as well be wishing for a free Ferrari, a Unicorn and a date with Mira Sorvino, but it would be great if D-Link released a 1.2x firmware with just the fix for this issue. Alas, it is unlikely.</p></htmltext>
<tokenext>That 's the latest I see too.My concern with the DIR-655 is that I 'm still at v1.21 [ HW rev A3 ] .
I 've read nothing but nightmare stories of people with perfectly stable 1.2x routers who then upgraded to 1.3X firmwares and had tons of trouble and instability .
At v1.21 my router is absolutely rock solid .
This is the best , most stable wireless router I 've ever had .
If the 1.21 firmware is affected , and I 'm forced to upgrade to 1.3X and it causes my router to become unstable , I 'm going to be PISSED ! I realize I might as well be wishing for a free Ferrari , a Unicorn and a date with Mira Sorvino , but it would be great if D-Link released a 1.2x firmware with just the fix for this issue .
Alas , it is unlikely .</tokentext>
<sentencetext>That's the latest I see too.My concern with the DIR-655 is that I'm still at v1.21 [HW rev A3].
I've read nothing but nightmare stories of people with perfectly stable 1.2x routers who then upgraded to 1.3X firmwares and had tons of trouble and instability.
At v1.21 my router is absolutely rock solid.
This is the best, most stable wireless router I've ever had.
If the 1.21 firmware is affected, and I'm forced to upgrade to 1.3X and it causes my router to become unstable, I'm going to be PISSED!I realize I might as well be wishing for a free Ferrari, a Unicorn and a date with Mira Sorvino, but it would be great if D-Link released a 1.2x firmware with just the fix for this issue.
Alas, it is unlikely.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815646</id>
	<title>Wow.</title>
	<author>Anonymous</author>
	<datestamp>1263830700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Who could possibly have suspected that silently enabling a "remote management" interface with weak authentication could possibly make a device less secure?<br> <br>

To whose benefit is this HNAC stuff, anyway? It seems to be largely invisible to the user and not aimed at them. Are ISPs supposed to be "managing" our routers now?</htmltext>
<tokenext>Who could possibly have suspected that silently enabling a " remote management " interface with weak authentication could possibly make a device less secure ?
To whose benefit is this HNAC stuff , anyway ?
It seems to be largely invisible to the user and not aimed at them .
Are ISPs supposed to be " managing " our routers now ?</tokentext>
<sentencetext>Who could possibly have suspected that silently enabling a "remote management" interface with weak authentication could possibly make a device less secure?
To whose benefit is this HNAC stuff, anyway?
It seems to be largely invisible to the user and not aimed at them.
Are ISPs supposed to be "managing" our routers now?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30822038</id>
	<title>Re:Problem Is More Widespread Than Reported!</title>
	<author>cyberjock1980</author>
	<datestamp>1263928860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So is a user better off using a Linux box as a router?  How about Windows Server 2008 R2?  Anyone know?</p></htmltext>
<tokenext>So is a user better off using a Linux box as a router ?
How about Windows Server 2008 R2 ?
Anyone know ?</tokentext>
<sentencetext>So is a user better off using a Linux box as a router?
How about Windows Server 2008 R2?
Anyone know?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816082</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816240</id>
	<title>DI-524 workaround?</title>
	<author>hobdes</author>
	<datestamp>1263837840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've got an affected router (DI-524 Rev C1 v3.23 firmware).  From the advisory:<blockquote><div><p>Older models, such as the DI-524, require authentication for all of the supported SOAP actions, but
allow both the administrator and user accounts to execute any of these actions. This allows a malicious
individual to use the often-ignored user account (default login of 'user' with a blank password) to
perform administrative actions</p></div>
</blockquote><p>

If I read that right I should be fine as long as I secure the user account as well as the admin account.  (And, of course, disable remote access.)

Can anybody confirm/correct?  Thanks.</p></div>
	</htmltext>
<tokenext>I 've got an affected router ( DI-524 Rev C1 v3.23 firmware ) .
From the advisory : Older models , such as the DI-524 , require authentication for all of the supported SOAP actions , but allow both the administrator and user accounts to execute any of these actions .
This allows a malicious individual to use the often-ignored user account ( default login of 'user ' with a blank password ) to perform administrative actions If I read that right I should be fine as long as I secure the user account as well as the admin account .
( And , of course , disable remote access .
) Can anybody confirm/correct ?
Thanks .</tokentext>
<sentencetext>I've got an affected router (DI-524 Rev C1 v3.23 firmware).
From the advisory:Older models, such as the DI-524, require authentication for all of the supported SOAP actions, but
allow both the administrator and user accounts to execute any of these actions.
This allows a malicious
individual to use the often-ignored user account (default login of 'user' with a blank password) to
perform administrative actions


If I read that right I should be fine as long as I secure the user account as well as the admin account.
(And, of course, disable remote access.
)

Can anybody confirm/correct?
Thanks.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816008</id>
	<title>Not afraid of this one</title>
	<author>Anonymous</author>
	<datestamp>1263834420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If you are that high tech, you probably would have a custom Router anyway?  Hmmmmm.</p></htmltext>
<tokenext>If you are that high tech , you probably would have a custom Router anyway ?
Hmmmmm .</tokentext>
<sentencetext>If you are that high tech, you probably would have a custom Router anyway?
Hmmmmm.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815734</id>
	<title>UBICOM Based Routers?</title>
	<author>Fnord666</author>
	<datestamp>1263831540000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>It looks like this might be a broader issue than just DLink routers.  Several comments on TFA seem to suggest that the HNAP remote management interface is a part of the SDK for the board used in these routers.  This implies that any router based on this board might have this vulnerability.  The <a href="http://www.dd-wrt.com/wiki/index.php/Known\_incompatible\_devices" title="dd-wrt.com">DD-WRT hardware incompatibility list</a> [dd-wrt.com] happens to have a list of routers that use UBICOM boards.</p><p>
Some other UBICOM based devices listed in TFA's comments include:
</p><ul>
<li>D-Link Wireless 108G Gaming Router</li><li>SMC Barricade SMCWGBR14-N</li><li>Netgear WNDR3700</li><li>ZyXEL's MIMO-N line</li></ul></htmltext>
<tokenext>It looks like this might be a broader issue than just DLink routers .
Several comments on TFA seem to suggest that the HNAP remote management interface is a part of the SDK for the board used in these routers .
This implies that any router based on this board might have this vulnerability .
The DD-WRT hardware incompatibility list [ dd-wrt.com ] happens to have a list of routers that use UBICOM boards .
Some other UBICOM based devices listed in TFA 's comments include : D-Link Wireless 108G Gaming RouterSMC Barricade SMCWGBR14-NNetgear WNDR3700ZyXEL 's MIMO-N line</tokentext>
<sentencetext>It looks like this might be a broader issue than just DLink routers.
Several comments on TFA seem to suggest that the HNAP remote management interface is a part of the SDK for the board used in these routers.
This implies that any router based on this board might have this vulnerability.
The DD-WRT hardware incompatibility list [dd-wrt.com] happens to have a list of routers that use UBICOM boards.
Some other UBICOM based devices listed in TFA's comments include:

D-Link Wireless 108G Gaming RouterSMC Barricade SMCWGBR14-NNetgear WNDR3700ZyXEL's MIMO-N line</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612</id>
	<title>Wouldn't the responsible thing be...</title>
	<author>Anonymous</author>
	<datestamp>1263830400000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>to contact D-Link first? Maybe D-Link could have updated the firmware before this exploit became public knowledge. I doubt SourceSec cares about D-Links customers.</htmltext>
<tokenext>to contact D-Link first ?
Maybe D-Link could have updated the firmware before this exploit became public knowledge .
I doubt SourceSec cares about D-Links customers .</tokentext>
<sentencetext>to contact D-Link first?
Maybe D-Link could have updated the firmware before this exploit became public knowledge.
I doubt SourceSec cares about D-Links customers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>davester666</author>
	<datestamp>1263832080000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>TFA mentions that DLink has published new firmware for the routers already.  But I've got a DIR-655/A4, and their support site still only lists firmware from last September (v1.32NA) and the firmware check in the router says it's the latest.  Where are these updated firmwares available?</p></htmltext>
<tokenext>TFA mentions that DLink has published new firmware for the routers already .
But I 've got a DIR-655/A4 , and their support site still only lists firmware from last September ( v1.32NA ) and the firmware check in the router says it 's the latest .
Where are these updated firmwares available ?</tokentext>
<sentencetext>TFA mentions that DLink has published new firmware for the routers already.
But I've got a DIR-655/A4, and their support site still only lists firmware from last September (v1.32NA) and the firmware check in the router says it's the latest.
Where are these updated firmwares available?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816356</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Farhood</author>
	<datestamp>1263840120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Gimme a minute to RTFA, and I'll check your router for you.</p></htmltext>
<tokenext>Gim me a minute to RTFA , and I 'll check your router for you .</tokentext>
<sentencetext>Gimme a minute to RTFA, and I'll check your router for you.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815978</id>
	<title>Just checked D-Link's website</title>
	<author>bytethese</author>
	<datestamp>1263834120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I don't see any update for the DIR-655, last firmware is from 07/2009, v1.32NA.<br> <br>

I hope they release soon, I know a few not so savvy users who have this model.</htmltext>
<tokenext>I do n't see any update for the DIR-655 , last firmware is from 07/2009 , v1.32NA .
I hope they release soon , I know a few not so savvy users who have this model .</tokentext>
<sentencetext>I don't see any update for the DIR-655, last firmware is from 07/2009, v1.32NA.
I hope they release soon, I know a few not so savvy users who have this model.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30826694</id>
	<title>Re:Don't make me upgrade to 1.3x!</title>
	<author>multisync</author>
	<datestamp>1263906660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I know the bug you're talking about, that seems to be more common with firmware versions later than 1.21. Connection to the outside slows to a crawl, then stops altogether. You can still talk to other machines on the LAN, but you can't get to the router's management page, so the only thing you can do is reset the device.</p><p>I've had this problem even with version 1.21 of the firmware, but the frequency has gone down dramatically over the past few months. I've only had to reset it once since the new year, so I am loath to update the firmware to a version that might increase the frequency of this problem. And, since D-Link has not acknowledged that the problem even exists (AFAIK), I doubt any firmware updates will make things better.</p></htmltext>
<tokenext>I know the bug you 're talking about , that seems to be more common with firmware versions later than 1.21 .
Connection to the outside slows to a crawl , then stops altogether .
You can still talk to other machines on the LAN , but you ca n't get to the router 's management page , so the only thing you can do is reset the device.I 've had this problem even with version 1.21 of the firmware , but the frequency has gone down dramatically over the past few months .
I 've only had to reset it once since the new year , so I am loath to update the firmware to a version that might increase the frequency of this problem .
And , since D-Link has not acknowledged that the problem even exists ( AFAIK ) , I doubt any firmware updates will make things better .</tokentext>
<sentencetext>I know the bug you're talking about, that seems to be more common with firmware versions later than 1.21.
Connection to the outside slows to a crawl, then stops altogether.
You can still talk to other machines on the LAN, but you can't get to the router's management page, so the only thing you can do is reset the device.I've had this problem even with version 1.21 of the firmware, but the frequency has gone down dramatically over the past few months.
I've only had to reset it once since the new year, so I am loath to update the firmware to a version that might increase the frequency of this problem.
And, since D-Link has not acknowledged that the problem even exists (AFAIK), I doubt any firmware updates will make things better.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816134</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815696</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Anonymous</author>
	<datestamp>1263831240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I don't think anyone on the planet can find a D-Link security contact.

More <a href="http://www.microsoft.com/security/msrc/report.aspx" title="microsoft.com" rel="nofollow">responsible</a> [microsoft.com] <a href="http://www.apple.com/support/security/" title="apple.com" rel="nofollow">companies</a> [apple.com] make this easy.</htmltext>
<tokenext>I do n't think anyone on the planet can find a D-Link security contact .
More responsible [ microsoft.com ] companies [ apple.com ] make this easy .</tokentext>
<sentencetext>I don't think anyone on the planet can find a D-Link security contact.
More responsible [microsoft.com] companies [apple.com] make this easy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816580</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Anonymous</author>
	<datestamp>1263843180000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Have you ever tried to contact D-Link?  Remember, they have DDOS'd NTP servers, and they continue to publish BUGGY dynamic DNS clients even when given bug reports.</p><p>D-Link outsources their routers to 3rd parties. The developers can not follow bug reports unless, sadly, they are written in Mandarin or Simple Chinese. And unless the bug report is blindingly and stupidly obvious (or on Slashdot), there's no one at D-Link US headquarters who cares enough to start a billable conversation with the contract developers. Don't expect D-Link QA in India to catch it - D-Link USA did not put this in the test plan! And the router tech support (all outsourced to India) doesn't gain anything by presenting issues back to Corporate.</p><p>Yes, I've worked with D-Link in one of the above scenarios. The best way to contact them is via a non-company contact, such as one of their major shareholders. I'm not fucking kidding either.<br>I'm posting this anonymously because my employer is one of the above mentioned groups, and for years we have been TRYING to get D-Link to fix bugs in their software which affect us.</p></htmltext>
<tokenext>Have you ever tried to contact D-Link ?
Remember , they have DDOS 'd NTP servers , and they continue to publish BUGGY dynamic DNS clients even when given bug reports.D-Link outsources their routers to 3rd parties .
The developers can not follow bug reports unless , sadly , they are written in Mandarin or Simple Chinese .
And unless the bug report is blindingly and stupidly obvious ( or on Slashdot ) , there 's no one at D-Link US headquarters who cares enough to start a billable conversation with the contract developers .
Do n't expect D-Link QA in India to catch it - D-Link USA did not put this in the test plan !
And the router tech support ( all outsourced to India ) does n't gain anything by presenting issues back to Corporate.Yes , I 've worked with D-Link in one of the above scenarios .
The best way to contact them is via a non-company contact , such as one of their major shareholders .
I 'm not fucking kidding either.I 'm posting this anonymously because my employer is one of the above mentioned groups , and for years we have been TRYING to get D-Link to fix bugs in their software which affect us .</tokentext>
<sentencetext>Have you ever tried to contact D-Link?
Remember, they have DDOS'd NTP servers, and they continue to publish BUGGY dynamic DNS clients even when given bug reports.D-Link outsources their routers to 3rd parties.
The developers can not follow bug reports unless, sadly, they are written in Mandarin or Simple Chinese.
And unless the bug report is blindingly and stupidly obvious (or on Slashdot), there's no one at D-Link US headquarters who cares enough to start a billable conversation with the contract developers.
Don't expect D-Link QA in India to catch it - D-Link USA did not put this in the test plan!
And the router tech support (all outsourced to India) doesn't gain anything by presenting issues back to Corporate.Yes, I've worked with D-Link in one of the above scenarios.
The best way to contact them is via a non-company contact, such as one of their major shareholders.
I'm not fucking kidding either.I'm posting this anonymously because my employer is one of the above mentioned groups, and for years we have been TRYING to get D-Link to fix bugs in their software which affect us.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815930</id>
	<title>It's IEs fault!</title>
	<author>Anonymous</author>
	<datestamp>1263833520000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext>Those niggers at Micro$oft fucked us again!</htmltext>
<tokenext>Those niggers at Micro $ oft fucked us again !</tokentext>
<sentencetext>Those niggers at Micro$oft fucked us again!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817388</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Anonymous</author>
	<datestamp>1263897120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I second that. No contact for security is available on any of their web pages and googling for one yields no result as well.<br>You can't really blame that you're not being notified if you do not provide a way for it.<br>Do they expect security researchers to phone them? perhaps at their customers support? at the researcher's expenses of course...</p></htmltext>
<tokenext>I second that .
No contact for security is available on any of their web pages and googling for one yields no result as well.You ca n't really blame that you 're not being notified if you do not provide a way for it.Do they expect security researchers to phone them ?
perhaps at their customers support ?
at the researcher 's expenses of course.. .</tokentext>
<sentencetext>I second that.
No contact for security is available on any of their web pages and googling for one yields no result as well.You can't really blame that you're not being notified if you do not provide a way for it.Do they expect security researchers to phone them?
perhaps at their customers support?
at the researcher's expenses of course...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815696</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30818570</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Chas</author>
	<datestamp>1263912900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No.  DLink's response to everything consumer-grade is is thus.

</p><ol>
<li>Act dumb (well, they're not REALLY acting)</li>
<li>Sit on hands</li>
<li>Offer an exchange</li>
<li>Hope the problem customer just "goes away".</li>
</ol><p>Years of experience with trying to get them to actually SUPPORT the crap they ship has taught me this.

</p><p>Their "pro grade" support is SLIGHTLY better.  But it's the difference between getting a root canal with no pain killers and getting a root canal with no pain killers while being repeatedly kneed in the nuts (which is ESPECIALLY impressive if you happen to be female).</p></htmltext>
<tokenext>No .
DLink 's response to everything consumer-grade is is thus .
Act dumb ( well , they 're not REALLY acting ) Sit on hands Offer an exchange Hope the problem customer just " goes away " .
Years of experience with trying to get them to actually SUPPORT the crap they ship has taught me this .
Their " pro grade " support is SLIGHTLY better .
But it 's the difference between getting a root canal with no pain killers and getting a root canal with no pain killers while being repeatedly kneed in the nuts ( which is ESPECIALLY impressive if you happen to be female ) .</tokentext>
<sentencetext>No.
DLink's response to everything consumer-grade is is thus.
Act dumb (well, they're not REALLY acting)
Sit on hands
Offer an exchange
Hope the problem customer just "goes away".
Years of experience with trying to get them to actually SUPPORT the crap they ship has taught me this.
Their "pro grade" support is SLIGHTLY better.
But it's the difference between getting a root canal with no pain killers and getting a root canal with no pain killers while being repeatedly kneed in the nuts (which is ESPECIALLY impressive if you happen to be female).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816206</id>
	<title>Let me be the first idiot to ask,</title>
	<author>Anonymous</author>
	<datestamp>1263837360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Does it matter, presuming your computers are all safely configured for direct connection to the net? Or does a vulnerable router mean you're wide open to say a man in the middle attack?</p></htmltext>
<tokenext>Does it matter , presuming your computers are all safely configured for direct connection to the net ?
Or does a vulnerable router mean you 're wide open to say a man in the middle attack ?</tokentext>
<sentencetext>Does it matter, presuming your computers are all safely configured for direct connection to the net?
Or does a vulnerable router mean you're wide open to say a man in the middle attack?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816940</id>
	<title>Re:Attack is Significant but Will not be Pandemic</title>
	<author>Anonymous</author>
	<datestamp>1263934500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If anyone has a DGL-4500 router, and experiences constant lockups with it (forced to power cycle the unit); your not alone. Apparently, there is a bug with DNS forwarding that started with firmware rev 1.21. It's been since July 2009, and the best you can hope for is an update still in beta. We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.</p></htmltext>
<tokenext>If anyone has a DGL-4500 router , and experiences constant lockups with it ( forced to power cycle the unit ) ; your not alone .
Apparently , there is a bug with DNS forwarding that started with firmware rev 1.21 .
It 's been since July 2009 , and the best you can hope for is an update still in beta .
We are talking about their newest high-end gaming router here with extra features that make a nice small office router too .</tokentext>
<sentencetext>If anyone has a DGL-4500 router, and experiences constant lockups with it (forced to power cycle the unit); your not alone.
Apparently, there is a bug with DNS forwarding that started with firmware rev 1.21.
It's been since July 2009, and the best you can hope for is an update still in beta.
We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30827622</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Anonymous</author>
	<datestamp>1263914520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This HNAP vulnerability exists in the latest North American firmware version, 1.32NA, for the D-Link DIR-655 router. There is no newer version of the North American DIR-655 firmware with a fix yet.</p></htmltext>
<tokenext>This HNAP vulnerability exists in the latest North American firmware version , 1.32NA , for the D-Link DIR-655 router .
There is no newer version of the North American DIR-655 firmware with a fix yet .</tokentext>
<sentencetext>This HNAP vulnerability exists in the latest North American firmware version, 1.32NA, for the D-Link DIR-655 router.
There is no newer version of the North American DIR-655 firmware with a fix yet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815746</id>
	<title>LOL, if they think ,,,,</title>
	<author>Anonymous</author>
	<datestamp>1263831720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>SourceSAC didn't come out of LOL town.</p></htmltext>
<tokenext>SourceSAC did n't come out of LOL town .</tokentext>
<sentencetext>SourceSAC didn't come out of LOL town.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816038</id>
	<title>I have nothing to contribute to this conversation</title>
	<author>Anrego</author>
	<datestamp>1263834660000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext><p>I really don't<nobr> <wbr></nobr>:(</p><p>Hopefully this whole thing gets corrected without too much harm<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>I really do n't : ( Hopefully this whole thing gets corrected without too much harm : )</tokentext>
<sentencetext>I really don't :(Hopefully this whole thing gets corrected without too much harm :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815754</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>OverlordQ</author>
	<datestamp>1263831840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>So, is it irony that their site links to "Ethical Hacker Network"?</p></htmltext>
<tokenext>So , is it irony that their site links to " Ethical Hacker Network " ?</tokentext>
<sentencetext>So, is it irony that their site links to "Ethical Hacker Network"?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815988</id>
	<title>Re:Attack is Significant but Will not be Pandemic</title>
	<author>MichaelSmith</author>
	<datestamp>1263834300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How about just busting into their wifi? There is an AP near the tram stop I use called "DLINK". I use it some times to check stuff while waiting for the tram to go. Now every time I go past an AP called DLINK (and there are a lot of them) ubuntu tries to connect. A lot of the time it gets on too.</p></htmltext>
<tokenext>How about just busting into their wifi ?
There is an AP near the tram stop I use called " DLINK " .
I use it some times to check stuff while waiting for the tram to go .
Now every time I go past an AP called DLINK ( and there are a lot of them ) ubuntu tries to connect .
A lot of the time it gets on too .</tokentext>
<sentencetext>How about just busting into their wifi?
There is an AP near the tram stop I use called "DLINK".
I use it some times to check stuff while waiting for the tram to go.
Now every time I go past an AP called DLINK (and there are a lot of them) ubuntu tries to connect.
A lot of the time it gets on too.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816456</id>
	<title>Re:DGL-4500 users left screwed</title>
	<author>Giometrix</author>
	<datestamp>1263841560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>If anyone has a DGL-4500 router, and experiences constant lockups with it (forced to power cycle the unit); your not alone. Apparently, there is a bug with DNS forwarding that started with firmware rev 1.21. It's been since July 2009, and the best you can hope for is an update still in beta. We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.</p><p>As it stands, users of this model are furious. Some are threatening a class-action lawsuit against them. By all means, please read through the D-Link forum before you think about buying one of their products.
<a href="http://forums.dlink.com/index.php?board=144.0" title="dlink.com">http://forums.dlink.com/index.php?board=144.0</a> [dlink.com] </p></div><p>Odd, I have this model... and with v1.15 (2008/10/29) the admin page says I have the latest version of the firmware. I wonder if they stopped pushing anything that came later.</p></div>
	</htmltext>
<tokenext>If anyone has a DGL-4500 router , and experiences constant lockups with it ( forced to power cycle the unit ) ; your not alone .
Apparently , there is a bug with DNS forwarding that started with firmware rev 1.21 .
It 's been since July 2009 , and the best you can hope for is an update still in beta .
We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.As it stands , users of this model are furious .
Some are threatening a class-action lawsuit against them .
By all means , please read through the D-Link forum before you think about buying one of their products .
http : //forums.dlink.com/index.php ? board = 144.0 [ dlink.com ] Odd , I have this model... and with v1.15 ( 2008/10/29 ) the admin page says I have the latest version of the firmware .
I wonder if they stopped pushing anything that came later .</tokentext>
<sentencetext>If anyone has a DGL-4500 router, and experiences constant lockups with it (forced to power cycle the unit); your not alone.
Apparently, there is a bug with DNS forwarding that started with firmware rev 1.21.
It's been since July 2009, and the best you can hope for is an update still in beta.
We are talking about their newest high-end gaming router here with extra features that make a nice small office router too.As it stands, users of this model are furious.
Some are threatening a class-action lawsuit against them.
By all means, please read through the D-Link forum before you think about buying one of their products.
http://forums.dlink.com/index.php?board=144.0 [dlink.com] Odd, I have this model... and with v1.15 (2008/10/29) the admin page says I have the latest version of the firmware.
I wonder if they stopped pushing anything that came later.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816144</id>
	<title>Re:DGL-4500 users left screwed</title>
	<author>Anonymous</author>
	<datestamp>1263836400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Who would pick anything D-Link/whatever over something as simple as m0n0wall or pfsense or IPCop for a small office? Sounds like someone hasn't been doing their homework.</p></htmltext>
<tokenext>Who would pick anything D-Link/whatever over something as simple as m0n0wall or pfsense or IPCop for a small office ?
Sounds like someone has n't been doing their homework .</tokentext>
<sentencetext>Who would pick anything D-Link/whatever over something as simple as m0n0wall or pfsense or IPCop for a small office?
Sounds like someone hasn't been doing their homework.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815594</id>
	<title>Where is CowboyNeal?</title>
	<author>Anonymous</author>
	<datestamp>1263830220000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext>You insensitive clod!  The Library of Congress isn't prime!</htmltext>
<tokenext>You insensitive clod !
The Library of Congress is n't prime !</tokentext>
<sentencetext>You insensitive clod!
The Library of Congress isn't prime!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815630</id>
	<title>fdsfds</title>
	<author>snj2010</author>
	<datestamp>1263830580000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><a href="http://www.bestugg.info/ugg-knightsbridge-c-49.html" title="bestugg.info" rel="nofollow">ugg knightsbridge sale</a> [bestugg.info]
<a href="http://www.bestugg.info/ugg-knightsbridge-c-49.html" title="bestugg.info" rel="nofollow">ugg knightsbridge shoe</a> [bestugg.info]
<a href="http://www.bestugg.info/ugg-knightsbridge-c-49.html" title="bestugg.info" rel="nofollow">ugg knightsbridge chestnut</a> [bestugg.info]</htmltext>
<tokenext>ugg knightsbridge sale [ bestugg.info ] ugg knightsbridge shoe [ bestugg.info ] ugg knightsbridge chestnut [ bestugg.info ]</tokentext>
<sentencetext>ugg knightsbridge sale [bestugg.info]
ugg knightsbridge shoe [bestugg.info]
ugg knightsbridge chestnut [bestugg.info]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816338</id>
	<title>Re:DGL-4500 users left screwed</title>
	<author>DigiShaman</author>
	<datestamp>1263839760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>For an office of say 10 employees, a SOHO router is just fine. It's cheap, easy to configure, and solid state. They can also be mounted on a telco baseboard along with the rest of the equipment too. Why cobble together a used PC (or new) to run M0n0wall for just 10 users? Not worth the time IMHO. Just plug in a WiFi Linksys box and be done with it!</p></htmltext>
<tokenext>For an office of say 10 employees , a SOHO router is just fine .
It 's cheap , easy to configure , and solid state .
They can also be mounted on a telco baseboard along with the rest of the equipment too .
Why cobble together a used PC ( or new ) to run M0n0wall for just 10 users ?
Not worth the time IMHO .
Just plug in a WiFi Linksys box and be done with it !</tokentext>
<sentencetext>For an office of say 10 employees, a SOHO router is just fine.
It's cheap, easy to configure, and solid state.
They can also be mounted on a telco baseboard along with the rest of the equipment too.
Why cobble together a used PC (or new) to run M0n0wall for just 10 users?
Not worth the time IMHO.
Just plug in a WiFi Linksys box and be done with it!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816144</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816082</id>
	<title>Problem Is More Widespread Than Reported!</title>
	<author>Anonymous</author>
	<datestamp>1263835380000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is nothing new. In fact, review the many easy hacks against several router manufacturers and you'll discover a lot of them (many exploiting uPnP) have FAILED to patch these issues for many YEARS. A good many of these routers are wired routers with the public being told to buy a wireless router instead (many of which remain unpatched to several malicious exploits!) when all they really want is wired. Many wise individuals do not want to go wi-fi nor should they be forced to do so.</p><p>Search for some of the exploits yourself, many of them uPnP, visit the router manufacturer's webpages listings for each of their routers, check their latest firmware update release and discover for yourself just how many routers haven't received any updates for years. What's even more shocking is many of these routers CONTINUE to be sold IN STORES and online, often the boxes still claiming how much security they offer when no firmware updates are available for many of them! Many old firmware patches resolve some issues with uPnP but do not offer protection against newer uPnP (and other) attacks!</p><p>This is clearly insane!</p><p>Router manufacturers should continue to patch old routers, especially those products of theirs still being sold in brick and mortar retail outlets!</p><p>This is obviously being swept under the rug, as many individuals who have been screaming on manufacturer's forums, mailing lists, e-mails, even via snail mail are being disregarded, posts/threads being shuffled off quietly, people being told to buy a newer router than the one at the store which claimed to offer a good degree of security, only to find their newer router purchased often with old firmware and no modern firmware available!</p><p>Governments and people need to hold these manufacturers accountable!</p></htmltext>
<tokenext>This is nothing new .
In fact , review the many easy hacks against several router manufacturers and you 'll discover a lot of them ( many exploiting uPnP ) have FAILED to patch these issues for many YEARS .
A good many of these routers are wired routers with the public being told to buy a wireless router instead ( many of which remain unpatched to several malicious exploits !
) when all they really want is wired .
Many wise individuals do not want to go wi-fi nor should they be forced to do so.Search for some of the exploits yourself , many of them uPnP , visit the router manufacturer 's webpages listings for each of their routers , check their latest firmware update release and discover for yourself just how many routers have n't received any updates for years .
What 's even more shocking is many of these routers CONTINUE to be sold IN STORES and online , often the boxes still claiming how much security they offer when no firmware updates are available for many of them !
Many old firmware patches resolve some issues with uPnP but do not offer protection against newer uPnP ( and other ) attacks ! This is clearly insane ! Router manufacturers should continue to patch old routers , especially those products of theirs still being sold in brick and mortar retail outlets ! This is obviously being swept under the rug , as many individuals who have been screaming on manufacturer 's forums , mailing lists , e-mails , even via snail mail are being disregarded , posts/threads being shuffled off quietly , people being told to buy a newer router than the one at the store which claimed to offer a good degree of security , only to find their newer router purchased often with old firmware and no modern firmware available ! Governments and people need to hold these manufacturers accountable !</tokentext>
<sentencetext>This is nothing new.
In fact, review the many easy hacks against several router manufacturers and you'll discover a lot of them (many exploiting uPnP) have FAILED to patch these issues for many YEARS.
A good many of these routers are wired routers with the public being told to buy a wireless router instead (many of which remain unpatched to several malicious exploits!
) when all they really want is wired.
Many wise individuals do not want to go wi-fi nor should they be forced to do so.Search for some of the exploits yourself, many of them uPnP, visit the router manufacturer's webpages listings for each of their routers, check their latest firmware update release and discover for yourself just how many routers haven't received any updates for years.
What's even more shocking is many of these routers CONTINUE to be sold IN STORES and online, often the boxes still claiming how much security they offer when no firmware updates are available for many of them!
Many old firmware patches resolve some issues with uPnP but do not offer protection against newer uPnP (and other) attacks!This is clearly insane!Router manufacturers should continue to patch old routers, especially those products of theirs still being sold in brick and mortar retail outlets!This is obviously being swept under the rug, as many individuals who have been screaming on manufacturer's forums, mailing lists, e-mails, even via snail mail are being disregarded, posts/threads being shuffled off quietly, people being told to buy a newer router than the one at the store which claimed to offer a good degree of security, only to find their newer router purchased often with old firmware and no modern firmware available!Governments and people need to hold these manufacturers accountable!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816104</id>
	<title>Re:Wouldn't the responsible thing be...</title>
	<author>Dan667</author>
	<datestamp>1263835860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>your going to use Microsoft as an example of what to do with security?  haha, that is funny.</htmltext>
<tokenext>your going to use Microsoft as an example of what to do with security ?
haha , that is funny .</tokentext>
<sentencetext>your going to use Microsoft as an example of what to do with security?
haha, that is funny.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815696</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816918</id>
	<title>DIR-615</title>
	<author>Nonillion</author>
	<datestamp>1263934260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maybe that's why the last DIR-615 was acting strange, I replaced it with another DIR-615 but it has firmware version C1. Guess I'm safe, for now..</p></htmltext>
<tokenext>Maybe that 's why the last DIR-615 was acting strange , I replaced it with another DIR-615 but it has firmware version C1 .
Guess I 'm safe , for now. .</tokentext>
<sentencetext>Maybe that's why the last DIR-615 was acting strange, I replaced it with another DIR-615 but it has firmware version C1.
Guess I'm safe, for now..</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815626</id>
	<title>Bad vendors</title>
	<author>Anonymous</author>
	<datestamp>1263830580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don't blame them. Finding security contacts for consumer hardware companies is next to impossible.

</p><p>Whether it is D-Link, Belkin, Netgear - I don't believe any of them have a public security page similar to any major software vendors.</p></htmltext>
<tokenext>I do n't blame them .
Finding security contacts for consumer hardware companies is next to impossible .
Whether it is D-Link , Belkin , Netgear - I do n't believe any of them have a public security page similar to any major software vendors .</tokentext>
<sentencetext>I don't blame them.
Finding security contacts for consumer hardware companies is next to impossible.
Whether it is D-Link, Belkin, Netgear - I don't believe any of them have a public security page similar to any major software vendors.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816508</id>
	<title>Only fools buy D-Link trash anyway</title>
	<author>Fotograf</author>
	<datestamp>1263842220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>from routers, switches to cameras, all i have seen is half finished overpriced junk</htmltext>
<tokenext>from routers , switches to cameras , all i have seen is half finished overpriced junk</tokentext>
<sentencetext>from routers, switches to cameras, all i have seen is half finished overpriced junk</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30819444
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815924
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815630
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815754
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816580
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30822038
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816082
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816338
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816144
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817036
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817388
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815696
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816456
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816940
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815846
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816104
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815696
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30826694
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816134
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816156
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815978
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30818570
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815686
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816356
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816856
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815630
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30827622
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_19_0147239_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817782
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815988
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815846
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815846
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815988
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817782
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816940
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815630
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816856
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815924
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30818652
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815626
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815612
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815754
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816580
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30818570
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815696
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816104
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817388
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815784
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30827622
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816356
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30817036
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816134
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30826694
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815686
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815978
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816156
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816918
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815914
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816038
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816206
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816082
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30822038
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815786
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816144
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816338
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30816456
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30819444
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815594
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815646
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_19_0147239.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_19_0147239.30815734
</commentlist>
</conversation>
