<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Idiot Hacker in </title>
<link>http://www.dslreports.com/forum/r18191932</link>
<description></description>
<language>en</language>
<pubDate>Tue, 09 Feb 2010 21:25:30 EDT</pubDate>
<lastBuildDate>Tue, 09 Feb 2010 21:25:30 EDT</lastBuildDate>

<item>
<title>Re: Idiot Hacker</title>
<link>http://www.dslreports.com/forum/remark,18193335</link>
<description><![CDATA[<A HREF="/useremail/u/775016"><b>snatman</b></A> : "12345!  Amazing, I got the same combination on my luggage!" /Spaceballs]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,18193335</guid>
<pubDate>Wed, 18 Apr 2007 14:58:03 EDT</pubDate>
</item>

<item>
<title>Re: Idiot Hacker</title>
<link>http://www.dslreports.com/forum/remark,18192343</link>
<description><![CDATA[<A HREF="/useremail/u/939879"><b>openbox9</b></A> : And both you and your ISP knew about this insecurity. Same practice as almost every networking device sold. It's not the same as looking for, or discovering a "vulnerability" and then contacting the responsible party for a fix...or worse yet, posting it on the net for potential malicious activity.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,18192343</guid>
<pubDate>Wed, 18 Apr 2007 12:15:12 EDT</pubDate>
</item>

<item>
<title>Re: Idiot Hacker</title>
<link>http://www.dslreports.com/forum/remark,18192198</link>
<description><![CDATA[<A HREF="/useremail/u/1278570"><b>gworkman7</b></A> : User:  Admin<br>Pass:  1234<br><br>Not very secure, but that was how my ISP was shipping their modems a couple of years back.  They were counting on self-installers to change the password when they got the modems.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,18192198</guid>
<pubDate>Wed, 18 Apr 2007 11:55:46 EDT</pubDate>
</item>

<item>
<title>Re: Idiot Hacker</title>
<link>http://www.dslreports.com/forum/remark,18192077</link>
<description><![CDATA[<A HREF="/useremail/u/939879"><b>openbox9</b></A> : <div class="bquote"><SMALL>said by  dwhayden <A HREF="/useremail/u/269615"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</SMALL><BR><BR>I made the decision to call the ISP instead of telling everyone else how to hack it.</DIV>This is generally the "socially accepted" avenue to taken by white hats and in general, better for the overall community than telling the whole world about the vulnerabilities. What this guy did is more black hat and he does deserve the consequences. Now if you had received little or no response from your ISP regarding the situation, the area becomes a little more grey, and usually you'll see the vulnerabilities published in an attempt to 'force' a response.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,18192077</guid>
<pubDate>Wed, 18 Apr 2007 11:30:23 EDT</pubDate>
</item>

<item>
<title>Idiot Hacker</title>
<link>http://www.dslreports.com/forum/remark,18191932</link>
<description><![CDATA[<A HREF="/useremail/u/269615"><b>dwhayden</b></A> : Many years ago I discovered a security backdoor to my ISPs remote access server where I had gained full rights over the system.  I made the decision to call the ISP instead of telling everyone else how to hack it.  They hooked me up with the head engineer, and we worked together to plug the hole.  The ISP was very grateful for the information, and gave me a year free access.  <br><br>This stupid hacker took a security vulnerability, and made it much worse by publishing the how-to with passwords.  The ISP was well within its rights to terminate this idiot's service.   Hopefully charges will be filed against him for hacking since it's so obvious his motivation was not to protect the ISP and its subs, but to gain recognition. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,18191932</guid>
<pubDate>Wed, 18 Apr 2007 11:03:52 EDT</pubDate>
</item>

</channel>
</rss>
