<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Linkedin users....password files hacked in Community Chat</title>
    <link>https://community.qvc.com/t5/Community-Chat/Linkedin-users-password-files-hacked/m-p/209131#M93033</link>
    <description>&lt;P&gt; see &lt;A href="http://money.cnn.com/2012/06/06/technology/linkedin-password-hack/" target="_blank"&gt;http://money.cnn.com/2012/06/06/technology/linkedin-password-hack/&lt;/A&gt;&lt;/P&gt; &lt;P&gt; &lt;/P&gt; &lt;P&gt;folks are recommending to change it, even though it currently looks like there is no way to tie back the user name and password together.&lt;/P&gt; &lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Wed, 06 Jun 2012 18:28:12 GMT</pubDate>
    <dc:creator>biancardi</dc:creator>
    <dc:date>2012-06-06T18:28:12Z</dc:date>
    <item>
      <title>Linkedin users....password files hacked</title>
      <link>https://community.qvc.com/t5/Community-Chat/Linkedin-users-password-files-hacked/m-p/209131#M93033</link>
      <description>&lt;P&gt; see &lt;A href="http://money.cnn.com/2012/06/06/technology/linkedin-password-hack/" target="_blank"&gt;http://money.cnn.com/2012/06/06/technology/linkedin-password-hack/&lt;/A&gt;&lt;/P&gt; &lt;P&gt; &lt;/P&gt; &lt;P&gt;folks are recommending to change it, even though it currently looks like there is no way to tie back the user name and password together.&lt;/P&gt; &lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 06 Jun 2012 18:28:12 GMT</pubDate>
      <guid>https://community.qvc.com/t5/Community-Chat/Linkedin-users-password-files-hacked/m-p/209131#M93033</guid>
      <dc:creator>biancardi</dc:creator>
      <dc:date>2012-06-06T18:28:12Z</dc:date>
    </item>
  </channel>
</rss>

