<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Admin Blog &#187; internet</title>
	<atom:link href="http://www.webadminblog.com/index.php/tag/internet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webadminblog.com</link>
	<description>Real Web Admins.  Real World Experience.</description>
	<lastBuildDate>Thu, 22 Jul 2010 16:18:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>The 10 Least-Likely and Most Dangerous People on the Internet</title>
		<link>http://www.webadminblog.com/index.php/2009/11/13/the-10-least-likely-and-most-dangerous-people-on-the-internet/</link>
		<comments>http://www.webadminblog.com/index.php/2009/11/13/the-10-least-likely-and-most-dangerous-people-on-the-internet/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 18:15:25 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[OWASP AppSec DC 2009]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[companies]]></category>
		<category><![CDATA[dangerous]]></category>
		<category><![CDATA[hansen]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[most]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[robert]]></category>
		<category><![CDATA[rsnake]]></category>
		<category><![CDATA[worst]]></category>

		<guid isPermaLink="false">http://www.webadminblog.com/?p=338</guid>
		<description><![CDATA[This presentation was by Robert "RSnake" Hansen and was designed to be a fun conversation to have over drinks with security people.  I feel privileged to have been one of those security people who he talked about this with beforehand.  A very interesting topic about the non-obvious threats that may or may not exist.   [...]]]></description>
			<content:encoded><![CDATA[<p>This presentation was by Robert "RSnake" Hansen and was designed to be a fun conversation to have over drinks with security people.  I feel privileged to have been one of those security people who he talked about this with beforehand.  A very interesting topic about the non-obvious threats that may or may not exist.   My notes are below:</p>
<p><span style="text-decoration: underline;"><strong>Why?</strong></span></p>
<ul>
<li>Because I use the Internet</li>
<li>Because I'm a target</li>
<li>Because most people don't know</li>
<li>Because it's a fun conversation to have over drinks with security guys</li>
<li>Maybe/hopefully you'll continue this conversation instead of just arguing!</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Ground Rules</strong></span></p>
<ul>
<li>Must be non-obvious and must be directly related to the Internet.  Not:
<ul>
<li>...the President or any other gov'ernment official</li>
<li>...or someone involved with SCADA Systems/Brick and mortar</li>
</ul>
</li>
<li>Must be in control of some infrastructure or software, etc</li>
<li>Must have the largest or widest negative impact possible for the least amount of work and least likelihood of being stopped</li>
<li>No magic - must be real and dangerous</li>
<li>They can't be "bad" people</li>
<li>You can't take this list too seriously</li>
</ul>
<p><span style="text-decoration: underline;"><strong>How I Got Started</strong></span></p>
<ul>
<li>Started thinking about core technologies that everything relies on</li>
<li>Made a big list</li>
<li>Shopped it around to dozens of security experts</li>
<li>Assigned an arbitrary, unscientific, hand-wavy, risk-rating system of my own design</li>
<li>Ranked them in order of how scared I am of them personally</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#10</strong></span></p>
<ul>
<li>John Doe at C|Net</li>
<li>Job: Network Engineer</li>
<li>Why: Controls com.com</li>
<li>Impact: Largest collection point of typo traffic both for web adn email.
<ul>
<li>Doesn't require anything overt or even indefensible</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#9</strong></span></p>
<ul>
<li>Giorgio Maone of NoScript</li>
<li>Job: Consultant</li>
<li>Why: Controls NoScript</li>
<li>Impact: Nearly every security researcher on the planet - complete compromise.  In general the most paranoid people on earth would be compromised.
<ul>
<li>Builds arbitrary whitelists (ebay.com)</li>
<li>Has changed functionality to subvert Adblock Plus</li>
</ul>
</li>
</ul>
<p><span id="more-338"></span></p>
<p><span style="text-decoration: underline;"><strong>#8</strong></span></p>
<ul>
<li>Eddy Nigg at StartCom Ltd...
<ul>
<li>or John Doe at SSL Cert Reseller</li>
</ul>
</li>
<li>Job: Developer/QA</li>
<li>Why: Has access to create wildcard SSL certs for any domain</li>
<li>Impact: Would allow an attacker to steal any information they were able to man in the middle.
<ul>
<li>Previously demonstrated bad security</li>
<li>Much smaller and therefore less controlled than Verisign or Thawt</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#7</strong></span></p>
<ul>
<li>John Doe at Authorize.net</li>
<li>Job: Network admin/Server admin</li>
<li>Why: Has the ability to see the vast majority of online transactions.</li>
<li>Impact: Would allow an attacker to get PII and credit card information for the bulk of the US online shopping population and many international shoppers as well</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#6 (RSnake recants this one after dinner last night)<br />
</strong></span></p>
<ul>
<li>John Doe at Mozilla</li>
<li>Job: Has check-in access</li>
<li>Why: Has the ability to change functionality within the browser, including installing new SSL certs.</li>
<li>Impact: Would allow the attacker to man in the middle and read all SSL traffic.
<ul>
<li>Almost no documentation</li>
<li>The verification process is very open and subject to tampering - meaning the update mechanism isn't probably much better</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#5</strong></span></p>
<ul>
<li>Chirag and Floyd at Adwords</li>
<li>Job: Whomever checks in code</li>
<li>Why: Has access to millions of websites because it is XSS</li>
<li>Impact: Can be leveraged for stealing cookies and hijacking web functionality
<ul>
<li>Is embedded in millions of web pages</li>
<li>Is already obfuscated heavily</li>
<li>Is seen daily by the bulk of the Internet population</li>
<li>Begs the question about CDNs in particular</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#4</strong></span></p>
<ul>
<li>John Doe at Google's Postini</li>
<li>Job: Programmer/Server admin</li>
<li>Why: Controls and can view the bulk of the world's email - including Gmail</li>
<li>Impact: Would enable attacker to steal credentials, spoof conversations, tamper with data, introduce malware, etc
<ul>
<li>More dangerous than Adwords because it's passive</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#3</strong></span></p>
<ul>
<li>John Doe at 1 Wilshire</li>
<li>Job: NOC Monkey</li>
<li>Why: One of the largest peering centers on the west coast</li>
<li>Impact: Can tamper with machines, install malware, inject malicious traffic, intercept communications, etc...
<ul>
<li>Most amount of data links in one physical location</li>
<li>CIA has already demonstrated interest in choke points in San Francisco as outed by Mark Klein</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#2</strong></span></p>
<ul>
<li>John Doe at gtei.net</li>
<li>Job: Network Admin/Server Admin</li>
<li>Why: Controls 4.2.2.2 and 4.2.2.3</li>
<li>Impact: Can be used to subvert a huge chunk of Internet traffic by giving erroneous DNS answers
<ul>
<li>Used by default in many devices</li>
<li>Used by tons of individuals and companies who are lazy</li>
<li>Can be used in very targeted attacks for a very short period of time</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>#1</strong></span></p>
<ul>
<li>John Doe at iDefense</li>
<li>Job: Security Engineer/Consultant</li>
<li>Why: Consults for and is owned by Verisign, who owns Network Solutions, who controls authoritative DNS for ".com"</li>
<li>Impact: Would allow the bulk of the Internet traffic to be modified
<ul>
<li>Heavily monitored and protected but still could lead to temporary and targeted compromise</li>
<li>More dangerous than 4.2.2.2 because it controls all of .com and not just a subset of users</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Disappointed?  Upset?</strong></span></p>
<p>The room is full of people who care that your feelings are hurt.</p>
<p>The List</p>
<ol>
<li>John Doe at iDefense</li>
<li>John Doe at gtei.net</li>
<li>John Doe at 1 Wilshire</li>
<li>John Doe at Google's Postini</li>
<li>Chirag and Floyd at Adwords</li>
<li>John Doe at Mozilla</li>
<li>John Doe at Authorize.net</li>
<li>Eddy Nigg at StartCom Ltd.</li>
<li>Giorgio Maone of NoScript</li>
<li>John Doe at C|Net</li>
</ol>
<p><span style="text-decoration: underline;"><strong>Questions/Comments?</strong></span></p>
<ul>
<li>Robert Hansen
<ul>
<li>Robert_at_sectheory d0t c0m</li>
<li>http://www.sectheory.com</li>
<li>http://ha.ckers.org/</li>
<li>Detecting Malice
<ul>
<li>http://www.detectmalice.com/</li>
</ul>
</li>
<li>XSS Book: XSS Exploits and Defense
<ul>
<li>ISBN: 1597491543</li>
</ul>
</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.webadminblog.com/index.php/2009/11/13/the-10-least-likely-and-most-dangerous-people-on-the-internet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deep Packet Inspection and the Loss of Privacy and Security on the Internet</title>
		<link>http://www.webadminblog.com/index.php/2009/03/24/deep-packet-inspection-and-the-loss-of-privacy-and-security-on-the-internet/</link>
		<comments>http://www.webadminblog.com/index.php/2009/03/24/deep-packet-inspection-and-the-loss-of-privacy-and-security-on-the-internet/#comments</comments>
		<pubDate>Tue, 24 Mar 2009 18:30:37 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[TRISC 2009]]></category>
		<category><![CDATA[deep]]></category>
		<category><![CDATA[dpi]]></category>
		<category><![CDATA[inspection]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[loss]]></category>
		<category><![CDATA[packet]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.webadminblog.com/?p=210</guid>
		<description><![CDATA[For my first session of the day on Tuesday of the TRISC 2009 conference I attended a presentation by Andrew MacFarlane from Data Foundry, Inc. on "Deep Packet Inspection and the Loss of Privacy and Security on the Internet".  While the concept of DPI is nothing new to me and I remember first hearing about [...]]]></description>
			<content:encoded><![CDATA[<p>For my first session of the day on Tuesday of the TRISC 2009 conference I attended a presentation by Andrew MacFarlane from Data Foundry, Inc. on "Deep Packet Inspection and the Loss of Privacy and Security on the Internet".  While the concept of DPI is nothing new to me and I remember first hearing about it around the FBI's Carnivore project, this particular use case was something that I hadn't heard about.  Apparently pretty much every Tier 1 ISP has hopped onboard the DPI bandwagon and is now using the technology for everything from traffic prioritization to targeted advertising.  To make matters worse, you automatically agree to this type of monitoring by accepting your ISP's terms of service.  Data Foundry has been one of the few ISP's who have spoken out against this practice, but unless more people (especially end-users) lobby their congressmen to remove this waiver of privacy rights as part of our terms of service acceptance, the future of privacy and security on the internet is awfully bleak.  My notes from the session are below:</p>
<p><span id="more-210"></span></p>
<ul>
<li>ISPs’ “advanced network management” practices are changing the way that bits are transmitted across the internet</li>
<li>Content of online communications is now inspected as it travels between endpoints</li>
<li>ISP customer contracts require users to consent to the monitoring of their online activities</li>
<li>ISPs claim increasing Internet traffic is leading to network congestion that requires new non-standard network mgmt practices</li>
<li>Many ISPs are introducing network systems that identify traffic by type or application to delay “low-priority” bits</li>
<li>One HD video download is roughly equivalent to visiting 35,000 web pages</li>
<li>A few users account for most of the downstream traffic.  Upstream disparity is even greater.</li>
<li>Mandatory and non-negotiable ISP customer contracts authorize the wholesale inspection of user communications.</li>
<li>As a condition of service, customers (individuals and businesses) must consent to this inspection</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Deep Packet Inspection</strong></span></p>
<ul>
<li>Network-level appliance that captures Internet traffic on ingress and egress.</li>
<li>Examination of the packet’s header information and payload (content).</li>
<li>Analysis of (up to) all 7 layers of the OSI model</li>
<li>Network-based parental controls, spam filtering, detection and protection against adware, spyware, malware, or viruses</li>
<li>Network-based bandwidth prioritization</li>
<li>Filtering of IP, child porn, and provider or government-determined “unacceptable” or “illegal” speech</li>
<li>Targeted advertising through monitoring and data-mining</li>
<li>Enforcement of “Net Neutrality” based “nondiscrimination” imperative</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Network-Level Targeted Advertising</strong></span></p>
<ul>
<li>In 2006 and 2007 Phorm and British Telecom began secretly monitoring 54,000 Internet users and testing DPI-facilitated targeted advertising</li>
<li>By the end of 2009, all British Telecom Internet users will be monitored and presented with targeted ads</li>
<li>In 2008, NebuAd partnered with 30 American ISPs to track users on the Internet and perform targeted advertising</li>
<li>Network-level targeted advertising uses DPI to monitor everything that users transmit or receive over their Internet access connections
<ul>
<li>Web browsing</li>
<li>E-mail</li>
<li>IM</li>
<li>Downloads</li>
<li>Applications and Devices</li>
</ul>
</li>
<li>Advertising systems generate a profile which is then sold</li>
</ul>
<p><span style="text-decoration: underline;"><strong>No Way to Opt-Out of DPI</strong></span></p>
<ul>
<li>ISPs claim that users can opt-out of targeted advertising by installing a cookie that will turn off the ads, but not the tracking
<ul>
<li>Purging cookies will re-opt-in users</li>
<li>Disabling cookies will default to opt-in</li>
</ul>
</li>
<li>ISPs provide now way for users to opt-out of the underlying DPI</li>
<li>New DPI systems can block, segregate, or defeat user encryption</li>
</ul>
<p><span style="text-decoration: underline;"><strong>DPI: Privacy Implications</strong></span></p>
<ul>
<li>Consent to monitoring is a waiver of privacy rights
<ul>
<li>Including automated, non-human inspection</li>
</ul>
</li>
<li>All privileges are waived on an inspection network</li>
<li>Private communications will be available to others through a 3rd party subpoena to the ISP with a showing of mere relevance, and without user notice</li>
<li>ISP TOS require businesses to consent to the monitoring of their online communications</li>
<li>Information gleaned from inspection can be used for any and all purposes by the ISP</li>
<li>Trade secrets, proprietary information, confidential communications, transaction records, customer lists, etc are all exposed</li>
<li>Businesses risk violating customer privacy laws
<ul>
<li>Allowing third party access to medical, tax, financial, and credit records is often prohibited</li>
</ul>
</li>
</ul>
<p><span style="text-decoration: underline;"><strong>Solutions to Protect Privacy on the Internet</strong></span></p>
<ul>
<li>DPI has legitimate uses and need not be banned</li>
<li>However, wiretapping without a warrant should require express, voluntary (opt-in) and informed user consent</li>
<li>Full and complete disclosure of inspection practices and legal consequences to users</li>
<li>Educated and voluntary consent is OK</li>
<li>Requiring consent as a condition of receiving service is not voluntary</li>
<li>Intrusive regulation by industry-captured regulators is the wrong way</li>
<li>Need an administrative or legislative declaration of a public policy against internet access contracts that fail to disclose practices and privacy implications and/or require waiver of privacy rights as a condition of service</li>
<li>Privacy is preserved without regulation</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.webadminblog.com/index.php/2009/03/24/deep-packet-inspection-and-the-loss-of-privacy-and-security-on-the-internet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A DoS We Can Believe In</title>
		<link>http://www.webadminblog.com/index.php/2009/01/21/a-dos-we-can-believe-in/</link>
		<comments>http://www.webadminblog.com/index.php/2009/01/21/a-dos-we-can-believe-in/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 20:58:46 +0000</pubDate>
		<dc:creator>Ernest</dc:creator>
				<category><![CDATA[Application Performance Management]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[obama]]></category>

		<guid isPermaLink="false">http://www.webadminblog.com/?p=171</guid>
		<description><![CDATA[We knew that the historic inauguration of Barack Obama would be generating a lot more Internet traffic than usual, both in general and specifically here at NI.  Being prudent Web Admin types, we checked around to make sure we thought that there wouldn't be any untoward effects on our Web site.  Like many corporate sites, [...]]]></description>
			<content:encoded><![CDATA[<p>We knew that the historic inauguration of Barack Obama would be generating a lot more Internet traffic than usual, both in general and specifically here at NI.  Being prudent Web Admin types, we checked around to make sure we thought that there wouldn't be any untoward effects on our Web site.  Like many corporate sites, we use the same pipe for inbound Internet client usage and outbound Web traffic, so employees streaming video to watch the event could pose a problem.  We got all thumbs up after consulting with our networking team, and decided to not even send any messaging asking people to avoid streaming.  But, we monitored the situation carefully as the day unwound.  Here's what we saw, just for your edification!</p>
<p>Our max inbound Internet throughput was 285 Mbps, about double our usual peak.  We saw a ni.com Web site performance degradation of about 25% for less than two hours according to our Keynote stats.  ni.com ASPs were affected proportionately which indicates the slowdown was Internet-wide and not unique to our specific Internet connection here in Austin.  The slowdown was less pronounced internationally, but still visible.  So in summary - not a global holocaust, but a noticeable bump.</p>
<p>Cacti graphs showing our Internet connection traffic:</p>
<p><img class="aligncenter size-full wp-image-172" title="obamabumpcactihrly" src="http://www.webadminblog.com/wp-content/uploads/2009/01/obamabumpcactihrly.png" alt="obamabumpcactihrly" width="591" height="257" /><img class="aligncenter size-full wp-image-173" title="obamabumpcactidaily" src="http://www.webadminblog.com/wp-content/uploads/2009/01/obamabumpcactidaily.png" alt="obamabumpcactidaily" width="591" height="257" /></p>
<p>Keynote graph of several of our Web assets, showing global response time in seconds:<img class="aligncenter size-full wp-image-174" title="obamabumpkeynote" src="http://www.webadminblog.com/wp-content/uploads/2009/01/obamabumpkeynote.png" alt="obamabumpkeynote" width="800" height="500" />Looking at the traffic specifically, there were two main standouts.  We had TCP 1935, which is Flash RTMP, peaking around 85 Mbps, and UDP 8247, which is a special CNN port (they use a plugin called "Octoshape" with their Flash streaming), peaking at 50 Mbps.   We have an overall presence of about 2500 people here at our Austin HQ on an average day, but we can't tell exactly how many were streaming.  (Our NetQoS setup shows us there were 13,600 'flows,' but every time a stream stops and starts that creates a new one - and the streams were hiccupping like crazy.  We'd have to do a bunch of Excel work to figure out max concurrent, and have better things to do.)</p>
<p>In terms of the streaming provider breakdown - since everyone uses Akamai now, the vast majority showed as "Akamai".  We could probably dig more to find out, but we don't really care all that much.  And, <a href="http://www.techcrunch.com/2009/01/21/the-day-live-web-video-streaming-failed-us/" target="_blank">many of the sources were overwhelmed</a>, which helped some.</p>
<p>We just wanted to share the data, in case anyone finds it helpful or interesting.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.webadminblog.com/index.php/2009/01/21/a-dos-we-can-believe-in/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why is anyone still using WEP?</title>
		<link>http://www.webadminblog.com/index.php/2008/05/24/why-is-anyone-still-using-wep/</link>
		<comments>http://www.webadminblog.com/index.php/2008/05/24/why-is-anyone-still-using-wep/#comments</comments>
		<pubDate>Sat, 24 May 2008 23:16:06 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Wireless Networks]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[equivalent]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[wep]]></category>
		<category><![CDATA[wireless]]></category>
		<category><![CDATA[wpa]]></category>
		<category><![CDATA[wpa2]]></category>

		<guid isPermaLink="false">http://webadminblog.com/?p=5</guid>
		<description><![CDATA[Wireless internet access is everywhere these days.  Everyone from restaurants and bars to the average Joe Homeowner has some sort of wifi network set up.  The problem is that they set up these networks without giving security a second thought (or even a first thought in most cases).  I was at the TRISC conference last month and heard [...]]]></description>
			<content:encoded><![CDATA[<p>Wireless internet access is everywhere these days.  Everyone from restaurants and bars to the average Joe Homeowner has some sort of wifi network set up.  The problem is that they set up these networks without giving security a second thought (or even a first thought in most cases).  I was at the TRISC conference last month and heard SimpleNomad say that he doesn't pay for internet access anywhere any more because there's always an unsecured or poorly secured wireless network wherever he goes.  Lately, I've been testing that and he's absolutely right.  I'm the only person on my block not running either an open network or a WEP "protected" network.  I was even at a local hospital the other day and their "secure" internal network was using WEP. </p>
<p>For those of you just catching up, WEP is an almost 10 year old wireless protocol whose intent was to encrypt your wireless transmissions.  The problem is that WEP uses a user-defined key along with an "initialization vector" (IV) to generate the RC4 traffic key used to encrypt your data.  If I can gather enough of these IV's, then I can figure out what the key is and your network is now pwned.  I can speed up this process by injecting my own packets and I can get your key in under 3 minutes.  How's that for security? </p>
<p>So, why is anyone still using WEP?  It was deprecated as a wireless privacy mechanism back in 2004.  It is easily cracked and provides slightly more security than running an open wireless network.  All that and when you buy a new wireless router it's most likely still pre-configured with WEP enabled.  On some of these older models better encryption standards such as WPA or WPA2 aren't even options.  With much of the wireless network setup falling into the hands of novice users, some of the responsibility lies with the router manufacturers for even allowing them to use WEP.  The rest, in my opinion, is on the users themselves, who put up these networks without being educated enough to do so.  You wouldn't put a door on your home without making sure the locks worked, would you?  How about buying a car where everyone with that model vehicle had your same key?  I think you get the picture. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.webadminblog.com/index.php/2008/05/24/why-is-anyone-still-using-wep/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
