<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: When firmware attacks! (DDoS by D-Link)</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<pubDate>Sun, 06 Jul 2008 12:08:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Richard Clayton</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-22331</link>
		<dc:creator>Richard Clayton</dc:creator>
		<pubDate>Wed, 13 Jun 2007 07:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-22331</guid>
		<description>Some time ago, when I last looked at the firmware, almost all the stratum 1 time servers were still present :-(  My recommendation is to set a local NTP server (usually at your ISP) in by hand... if it doesn't respond then you should be looking at firewall policies.</description>
		<content:encoded><![CDATA[<p>Some time ago, when I last looked at the firmware, almost all the stratum 1 time servers were still present <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' />  My recommendation is to set a local NTP server (usually at your ISP) in by hand&#8230; if it doesn&#8217;t respond then you should be looking at firewall policies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pasi</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-22330</link>
		<dc:creator>Pasi</dc:creator>
		<pubDate>Wed, 13 Jun 2007 06:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-22330</guid>
		<description>When I change the time mode to manual in my dlink 614+ it still tries to contact ntp in 30 seconds interwall.  Logfile is filled with "get Time fail" and "NTP: timeout, no receive any data". And yes, I have updated the firmware to the latest with revision info "Fixes an issue with NTP server" but it still keeps trying that NTP. 

Is this firmware update just a removal of Kamps NTP-server from the NTP list or what?</description>
		<content:encoded><![CDATA[<p>When I change the time mode to manual in my dlink 614+ it still tries to contact ntp in 30 seconds interwall.  Logfile is filled with &#8220;get Time fail&#8221; and &#8220;NTP: timeout, no receive any data&#8221;. And yes, I have updated the firmware to the latest with revision info &#8220;Fixes an issue with NTP server&#8221; but it still keeps trying that NTP. </p>
<p>Is this firmware update just a removal of Kamps NTP-server from the NTP list or what?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Klaus</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-12710</link>
		<dc:creator>David Klaus</dc:creator>
		<pubDate>Sun, 07 Jan 2007 05:04:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-12710</guid>
		<description>Just a heads up.   I purchased a new piece of DLink hardware and they now show the following NTP servers in a setup list:

ntp1.dlink.com
ntp.dlink.com.tw

I checked and both seem to be working.</description>
		<content:encoded><![CDATA[<p>Just a heads up.   I purchased a new piece of DLink hardware and they now show the following NTP servers in a setup list:</p>
<p>ntp1.dlink.com<br />
ntp.dlink.com.tw</p>
<p>I checked and both seem to be working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: They do the same to DynDns</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-8571</link>
		<dc:creator>They do the same to DynDns</dc:creator>
		<pubDate>Wed, 13 Dec 2006 02:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-8571</guid>
		<description>Many DLink routers also display the same lack of respect for the DynDns service (Dynamic IP's).

DynDns was forced some years ago to block all traffic from DLink routers because they would not obey the procedures laid out for updating one's dynamic host name. (One update only ever 28 days or so, and ONLY if your IP address has changed). DLink also do not provide a valid ID string when sending the requests.

On the subject of my DI-604's NTP setting: sure, I can change it, along with the other fields on the form, but after submitting the changes, I see no evidence that the information was kept. The form reloads with the same default information, leading me to wonder if the DI 604 is even using the configuration I entered.

DI 604 rev A, B &#38; C last firmware was 2.20. I feel there is almost no chance there will ever be another official update patch. Indeed, I found this page by looking for a hacked firmware update.</description>
		<content:encoded><![CDATA[<p>Many DLink routers also display the same lack of respect for the DynDns service (Dynamic IP&#8217;s).</p>
<p>DynDns was forced some years ago to block all traffic from DLink routers because they would not obey the procedures laid out for updating one&#8217;s dynamic host name. (One update only ever 28 days or so, and ONLY if your IP address has changed). DLink also do not provide a valid ID string when sending the requests.</p>
<p>On the subject of my DI-604&#8217;s NTP setting: sure, I can change it, along with the other fields on the form, but after submitting the changes, I see no evidence that the information was kept. The form reloads with the same default information, leading me to wonder if the DI 604 is even using the configuration I entered.</p>
<p>DI 604 rev A, B &amp; C last firmware was 2.20. I feel there is almost no chance there will ever be another official update patch. Indeed, I found this page by looking for a hacked firmware update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Criggie</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-590</link>
		<dc:creator>Criggie</dc:creator>
		<pubDate>Thu, 15 Jun 2006 20:47:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-590</guid>
		<description>I routinely set NTP update intervals to 1440 or a few minutes less.  The recommended update time of 300 minutes seems too short... and if my clocks drift by some seconds then no great loss.

I also run a local timeserver just for work's network.

What would make life much more useful would be if DHCP could carry information on all settings...  ideally http_proxy as well as time_server and so on.</description>
		<content:encoded><![CDATA[<p>I routinely set NTP update intervals to 1440 or a few minutes less.  The recommended update time of 300 minutes seems too short&#8230; and if my clocks drift by some seconds then no great loss.</p>
<p>I also run a local timeserver just for work&#8217;s network.</p>
<p>What would make life much more useful would be if DHCP could carry information on all settings&#8230;  ideally http_proxy as well as time_server and so on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Light Blue Touchpaper &#187; The Rising Tide: DDoS by Defective Designs and Defaults</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-565</link>
		<dc:creator>Light Blue Touchpaper &#187; The Rising Tide: DDoS by Defective Designs and Defaults</dc:creator>
		<pubDate>Wed, 07 Jun 2006 21:32:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-565</guid>
		<description>[...] Dedicated readers will recall my article about how I tracked down the &#8220;DDoS&#8221; attack on stratum 1 time servers by various D-Link devices. I&#8217;ve now had a paper accepted at the 2nd Workshop on Steps to Reducing Unwanted Traffic on the Internet (SRUTI&#8217;06) which runs in California in early July. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dedicated readers will recall my article about how I tracked down the &#8220;DDoS&#8221; attack on stratum 1 time servers by various D-Link devices. I&#8217;ve now had a paper accepted at the 2nd Workshop on Steps to Reducing Unwanted Traffic on the Internet (SRUTI&#8217;06) which runs in California in early July. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al Bounds</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-413</link>
		<dc:creator>Al Bounds</dc:creator>
		<pubDate>Mon, 08 May 2006 13:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-413</guid>
		<description>D-Link's attitude in this matter is very simmilar to how they treated me when my D-Link WAP died for a third time while under warranty. Glad it was mine and not one of my customers! I made the descision to stay away from D-Link a few months ago and this story supports that descision. Bad product, bad company, bad attitude.</description>
		<content:encoded><![CDATA[<p>D-Link&#8217;s attitude in this matter is very simmilar to how they treated me when my D-Link WAP died for a third time while under warranty. Glad it was mine and not one of my customers! I made the descision to stay away from D-Link a few months ago and this story supports that descision. Bad product, bad company, bad attitude.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Gore</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-411</link>
		<dc:creator>Tony Gore</dc:creator>
		<pubDate>Sun, 07 May 2006 11:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-411</guid>
		<description>The ISPs could be more helpful and give their NTP server details prominently to their customers. Sometimes they require a lot of searching for.

The Belkin router I have only has a list of IP addresses to choose for NTP; the default for Europe is 129.132.2.21 which resolves to swisstime.ee.ethz.ch and the secondary default is 130.149.17.8 which is ntps1-1.cs.tu-berlin.de. There is no way to actually change these, as they are a drop down list. It does seem that unless these people have agreed to "host" NTP for Belkin, then Belkin are guilty of abuse - just as any SMTP server originally could be used for sending mail, and abuse by spammers put a stop to that.


Microsoft in http://support.microsoft.com/kb/262680/en-us gives a list of public timeservers. At no point does it mention that your ISP timeserver is better placed to do the job. If you run a Windows server system, time is important to you - clients cannot log on to the server if their time and date vary too much from the server, at least with SBS2003.

Routers may not be the only culprit - the Symantec hardware frewalls e.g. my 200R use "default timeservers" without saying which ones they are. However, you can enter your own timeserver.

There are other devices as well - my D-link DCS-900 wired camera has an NTP server - for this, you have to enter an IP address. (I had been a good boy and resolved ntp.demon.co.uk - my ISP and entered that one).

It seems to me, coming back to the ISP point, that ISPs should produce a list of things to use - both by name and by IP address. They should state that the name should be used in preference to the IP address (and equipment manufactures should be pushed to use names, not IP addresses).

After all, it is in their best interests - very NTP packet that goes out of the ISP's network costs them more than if they handled it themselves.</description>
		<content:encoded><![CDATA[<p>The ISPs could be more helpful and give their NTP server details prominently to their customers. Sometimes they require a lot of searching for.</p>
<p>The Belkin router I have only has a list of IP addresses to choose for NTP; the default for Europe is 129.132.2.21 which resolves to swisstime.ee.ethz.ch and the secondary default is 130.149.17.8 which is ntps1-1.cs.tu-berlin.de. There is no way to actually change these, as they are a drop down list. It does seem that unless these people have agreed to &#8220;host&#8221; NTP for Belkin, then Belkin are guilty of abuse - just as any SMTP server originally could be used for sending mail, and abuse by spammers put a stop to that.</p>
<p>Microsoft in <a href="http://support.microsoft.com/kb/262680/en-us" rel="nofollow">http://support.microsoft.com/kb/262680/en-us</a> gives a list of public timeservers. At no point does it mention that your ISP timeserver is better placed to do the job. If you run a Windows server system, time is important to you - clients cannot log on to the server if their time and date vary too much from the server, at least with SBS2003.</p>
<p>Routers may not be the only culprit - the Symantec hardware frewalls e.g. my 200R use &#8220;default timeservers&#8221; without saying which ones they are. However, you can enter your own timeserver.</p>
<p>There are other devices as well - my D-link DCS-900 wired camera has an NTP server - for this, you have to enter an IP address. (I had been a good boy and resolved ntp.demon.co.uk - my ISP and entered that one).</p>
<p>It seems to me, coming back to the ISP point, that ISPs should produce a list of things to use - both by name and by IP address. They should state that the name should be used in preference to the IP address (and equipment manufactures should be pushed to use names, not IP addresses).</p>
<p>After all, it is in their best interests - very NTP packet that goes out of the ISP&#8217;s network costs them more than if they handled it themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Daugherty</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-409</link>
		<dc:creator>Scott Daugherty</dc:creator>
		<pubDate>Sat, 06 May 2006 15:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-409</guid>
		<description>I found this a good read for I have a D-link wireless router.  I had the router for some time now but notice I could not set ntp when I bought it.  Last year I set up a vpn and converted the d-link to access point duties now but I had updated the firm ware at the time.  D-link states the firm ware update fixes the NTP issue.  I then pointed the NTP to a local host computer.  I just checked it and it is still correct.  I hope D-link owns up to being responsible as indicated above.  D-link should.  Now that I know this I will update firm ware on other networks I know of using d-link products too.</description>
		<content:encoded><![CDATA[<p>I found this a good read for I have a D-link wireless router.  I had the router for some time now but notice I could not set ntp when I bought it.  Last year I set up a vpn and converted the d-link to access point duties now but I had updated the firm ware at the time.  D-link states the firm ware update fixes the NTP issue.  I then pointed the NTP to a local host computer.  I just checked it and it is still correct.  I hope D-link owns up to being responsible as indicated above.  D-link should.  Now that I know this I will update firm ware on other networks I know of using d-link products too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ameliorations &#187; Stop the Presses!</title>
		<link>http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-403</link>
		<dc:creator>Ameliorations &#187; Stop the Presses!</dc:creator>
		<pubDate>Thu, 27 Apr 2006 16:21:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/#comment-403</guid>
		<description>[...] I have an update for anyone intereseted on the D-Link situation. Its hard to believe there are those who would question the efficiency of the threat of boycott coupled with a letter writing and blogging campaign. [...]</description>
		<content:encoded><![CDATA[<p>[...] I have an update for anyone intereseted on the D-Link situation. Its hard to believe there are those who would question the efficiency of the threat of boycott coupled with a letter writing and blogging campaign. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
