<?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>IPHere &#187; Fumble</title> <atom:link href="https://www.iphere.com/tag/fumble/feed" rel="self" type="application/rss+xml" /><link>https://www.iphere.com</link> <description>We show your current IP</description> <lastBuildDate>Wed, 03 Aug 2022 14:13:56 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.6.1</generator> <item><title>Cisco Password Fumble: Hardware Security At Risk</title><link>https://www.iphere.com/cisco-password-fumble-hardware-security-at-risk</link> <comments>https://www.iphere.com/cisco-password-fumble-hardware-security-at-risk#comments</comments> <pubDate>Thu, 21 Mar 2013 14:14:16 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Cisco]]></category> <category><![CDATA[Fumble]]></category> <category><![CDATA[Hardware]]></category> <category><![CDATA[Password]]></category> <category><![CDATA[Risk]]></category> <category><![CDATA[Security]]></category> <guid
isPermaLink="false">http://www.iphere.com/cisco-password-fumble-hardware-security-at-risk</guid> <description><![CDATA[Cisco has released a security bulletin warning that a move to strengthen passwords on some devices resulted in making passwords much easier to crack. The vulnerability affects recently released versions of the IOS and IOS XE operating system that runs on Cisco routers and switches. The problem stems from Cisco&#8217;s use of the Type 4 [&#8230;]]]></description> <wfw:commentRss>https://www.iphere.com/cisco-password-fumble-hardware-security-at-risk/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>