<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">

<channel rdf:about="http://it.slashdot.org/">
<title>Slashdot: IT</title>
<link>http://it.slashdot.org/</link>
<description>News for nerds, stuff that matters</description>
<dc:language>en-us</dc:language>
<dc:rights>Copyright 1997-2008, SourceForge, Inc.  All Rights Reserved.</dc:rights>
<dc:date>2008-05-13T04:00:23+00:00</dc:date>
<dc:publisher>SourceForge, Inc.</dc:publisher>
<dc:creator>help@slashdot.org</dc:creator>
<dc:subject>Technology</dc:subject>
<syn:updatePeriod>hourly</syn:updatePeriod>
<syn:updateFrequency>1</syn:updateFrequency>
<syn:updateBase>1970-01-01T00:00+00:00</syn:updateBase>
<items>
 <rdf:Seq>
  <rdf:li rdf:resource="http://it.slashdot.org/article.pl?sid=08/05/12/1926247&amp;from=rss" />
  <rdf:li rdf:resource="http://it.slashdot.org/article.pl?sid=08/05/12/1219241&amp;from=rss" />
  <rdf:li rdf:resource="http://tech.slashdot.org/article.pl?sid=08/05/12/0047253&amp;from=rss" />
  <rdf:li rdf:resource="http://developers.slashdot.org/article.pl?sid=08/05/11/219231&amp;from=rss" />
  <rdf:li rdf:resource="http://it.slashdot.org/article.pl?sid=08/05/11/2044216&amp;from=rss" />
  <rdf:li rdf:resource="http://tech.slashdot.org/article.pl?sid=08/05/11/1939240&amp;from=rss" />
  <rdf:li rdf:resource="http://developers.slashdot.org/article.pl?sid=08/05/11/1759213&amp;from=rss" />
  <rdf:li rdf:resource="http://linux.slashdot.org/article.pl?sid=08/05/11/1524236&amp;from=rss" />
  <rdf:li rdf:resource="http://it.slashdot.org/article.pl?sid=08/05/11/1339228&amp;from=rss" />
  <rdf:li rdf:resource="http://tech.slashdot.org/article.pl?sid=08/05/11/120216&amp;from=rss" />
  <rdf:li rdf:resource="http://it.slashdot.org/article.pl?sid=08/05/11/0327203&amp;from=rss" />
  <rdf:li rdf:resource="http://it.slashdot.org/article.pl?sid=08/05/11/014234&amp;from=rss" />
  <rdf:li rdf:resource="http://it.slashdot.org/article.pl?sid=08/05/09/164201&amp;from=rss" />
  <rdf:li rdf:resource="http://tech.slashdot.org/article.pl?sid=08/05/09/1258229&amp;from=rss" />
  <rdf:li rdf:resource="http://news.slashdot.org/article.pl?sid=08/05/08/2222254&amp;from=rss" />
 </rdf:Seq>
</items>
<image rdf:resource="http://images.slashdot.org/topics/topicslashdot.gif" />
<textinput rdf:resource="http://it.slashdot.org/search.pl" />
</channel>

<image rdf:about="http://images.slashdot.org/topics/topicslashdot.gif">
<title>Slashdot: IT</title>
<url>http://images.slashdot.org/topics/topicslashdot.gif</url>
<link>http://it.slashdot.org/</link>
</image>

<item rdf:about="http://it.slashdot.org/article.pl?sid=08/05/12/1926247&amp;from=rss">
<title>FTC to Scrutinize Contactless Payment Technology</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288909089/article.pl</link>
<description>coondoggie writes to tell us that the Federal Trade Commission (FTC) will be taking a look at contactless payment systems and the consumer protection issue surrounding them. "RFID technology provides obvious benefits, the FTC said. For example, the ability of producers using RFID to track exactly where in the supply chain their products are and by which retailer they were ultimately sold to a consumer has the potential to make product recalls more effective. However, there also may be costs regarding consumers' individual privacy rights associated with it."&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/12/1926247&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/12/1926247"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/12/1926247&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=gTcz5o"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=gTcz5o" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288909089" height="1" width="1"/&gt;</description>
<dc:creator>ScuttleMonkey</dc:creator>
<dc:date>2008-05-12T19:34:00+00:00</dc:date>
<dc:subject>security</dc:subject>
<slash:department>after-they-are-already-in-passports</slash:department>
<slash:section>it</slash:section>
<slash:comments>89</slash:comments>
<slash:hit_parade>89,89,73,65,29,17,6</slash:hit_parade>
<feedburner:origLink>http://it.slashdot.org/article.pl?sid=08/05/12/1926247&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://it.slashdot.org/article.pl?sid=08/05/12/1219241&amp;from=rss">
<title>DVD Porn Viruses Ravage US Soldiers' Computers</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288670093/article.pl</link>
<description>stevegee58 writes "Tom Ricks' Inbox in the Sunday Washington Post reported that bootleg DVDs purchased in Iraqi markets ("souks") are frequently infected with viruses. Iraqi soldiers were affected as well; electronic interaction between Iraqi and US soldiers frequently resulted in a corresponding exchange of viruses from these infected DVDs."&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/12/1219241&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/12/1219241"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/12/1219241&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=z2LEtq"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=z2LEtq" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288670093" height="1" width="1"/&gt;</description>
<dc:creator>CmdrTaco</dc:creator>
<dc:date>2008-05-12T12:48:00+00:00</dc:date>
<dc:subject>security</dc:subject>
<slash:department>oh-the-humanity</slash:department>
<slash:section>it</slash:section>
<slash:comments>425</slash:comments>
<slash:hit_parade>425,417,334,249,87,60,44</slash:hit_parade>
<feedburner:origLink>http://it.slashdot.org/article.pl?sid=08/05/12/1219241&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://tech.slashdot.org/article.pl?sid=08/05/12/0047253&amp;from=rss">
<title>XP SP3 Crashes Some AMD Machines</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288395021/article.pl</link>
<description>Stony Stevenson alerts us to new information on the XP SP3-induced crashes that we discussed a few days back. Jesper Johansson, a former program manager for security policy at Microsoft, is maintaining an ongoing log and support site for users affected by any of several problems triggered by XP3. Machines using AMD hardware, particularly HP desktops, seem to have several modes of failure; others affect Intel machines.&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/12/0047253&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/12/0047253"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/12/0047253&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=aDzHsv"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=aDzHsv" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288395021" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-12T02:49:00+00:00</dc:date>
<dc:subject>windows</dc:subject>
<slash:department>workarounds-emerge</slash:department>
<slash:section>tech</slash:section>
<slash:comments>240</slash:comments>
<slash:hit_parade>240,232,186,133,77,43,29</slash:hit_parade>
<feedburner:origLink>http://tech.slashdot.org/article.pl?sid=08/05/12/0047253&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://developers.slashdot.org/article.pl?sid=08/05/11/219231&amp;from=rss">
<title>Recruitment Options For a Small-Scale FOSS Project?</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288259766/article.pl</link>
<description>thermian writes "I've been developing my open source project for several years now, and I've never found a solution to one fairly important issue. How can a small-scale project attract new members? My project is pretty specialist, (no URL, sorry, I can't afford to get my server nuked) and I find that while it gets a fair bit of use, most users come to my software out of a need to solve their problem, or use my tutorials to learn about the subject, and none seem inclined to stick around and help make the product better. This is a fairly serious problem for me now, because my software has recently been adopted by a university, and I'm just not in a position to manage the entire set of applications and update everything on my own. Just preparing a version for release to students has been especially hard. The open source maxim 'Many eyes make all bugs shallow' only works if those 'many eyes' are available. So do you have any suggestions as to how, and where, to find people who fancy joining open source projects?"&lt;p&gt;&lt;a href="http://developers.slashdot.org/article.pl?sid=08/05/11/219231&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/219231"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://developers.slashdot.org/article.pl?sid=08/05/11/219231&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=cK2K5h"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=cK2K5h" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288259766" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-12T00:54:00+00:00</dc:date>
<dc:subject>programming</dc:subject>
<slash:department>where-is-everybody</slash:department>
<slash:section>developers</slash:section>
<slash:comments>197</slash:comments>
<slash:hit_parade>197,183,157,117,49,32,19</slash:hit_parade>
<feedburner:origLink>http://developers.slashdot.org/article.pl?sid=08/05/11/219231&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://it.slashdot.org/article.pl?sid=08/05/11/2044216&amp;from=rss">
<title>Hiding a Rootkit In System Management Mode</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288304936/article.pl</link>
<description>Sniper223 notes a PC World article on a new kind of rootkit recently developed by researchers, which will be demoed at Black Hat in August. The rootkit runs in System Management Mode, a longtime feature of x86 architecture that allows for code to run in a locked part of memory. It is said to be harder to detect, potentially, than VM-based rootkits. The article notes that the technique is unlikely to lead to widespread expoitation: "Being divorced from the operating system makes the SMM rootkit stealthy, but it also means that hackers have to write this driver code expressly for the system they are attacking."&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/2044216&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/2044216"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/2044216&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=TmJnbI"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=TmJnbI" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288304936" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-11T22:57:00+00:00</dc:date>
<dc:subject>security</dc:subject>
<slash:department>can-you-see-me-now</slash:department>
<slash:section>it</slash:section>
<slash:comments>116</slash:comments>
<slash:hit_parade>116,112,82,63,29,17,10</slash:hit_parade>
<feedburner:origLink>http://it.slashdot.org/article.pl?sid=08/05/11/2044216&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://tech.slashdot.org/article.pl?sid=08/05/11/1939240&amp;from=rss">
<title>Changes In Store For PHP V6</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288278037/article.pl</link>
<description>An anonymous reader sends in an IBM DeveloperWorks article detailing the changes coming in PHP V6 &amp;mdash; from namespaces, to Web 2.0 built-ins, to a few features that are being removed.&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/11/1939240&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/1939240"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/11/1939240&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=PzvrMR"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=PzvrMR" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288278037" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-11T21:47:00+00:00</dc:date>
<dc:subject>php</dc:subject>
<slash:department>ready-or-not</slash:department>
<slash:section>tech</slash:section>
<slash:comments>353</slash:comments>
<slash:hit_parade>353,344,275,199,56,24,16</slash:hit_parade>
<feedburner:origLink>http://tech.slashdot.org/article.pl?sid=08/05/11/1939240&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://developers.slashdot.org/article.pl?sid=08/05/11/1759213&amp;from=rss">
<title>What Is the Oldest Code Written Still Running?</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288219804/article.pl</link>
<description>Consul writes "What is the oldest piece of code that is still in use today, that has not actually been retyped or reimplemented in some way? By 'piece of code,' I'm of course referring to a complete algorithm, and not just a single line." The question would have a different answer if emulation, in multiple layers, is allowed.&lt;p&gt;&lt;a href="http://developers.slashdot.org/article.pl?sid=08/05/11/1759213&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/1759213"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://developers.slashdot.org/article.pl?sid=08/05/11/1759213&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=hkurcL"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=hkurcL" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288219804" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-11T19:30:00+00:00</dc:date>
<dc:subject>programming</dc:subject>
<slash:department>when-dinosaurs-ruled-the-datacenter</slash:department>
<slash:section>developers</slash:section>
<slash:comments>858</slash:comments>
<slash:hit_parade>858,845,665,460,123,74,45</slash:hit_parade>
<feedburner:origLink>http://developers.slashdot.org/article.pl?sid=08/05/11/1759213&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://linux.slashdot.org/article.pl?sid=08/05/11/1524236&amp;from=rss">
<title>How the NSA Took Linux To the Next Level</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288124397/article.pl</link>
<description>An anonymous reader brings us IBM Developerworks' recent analysis of how the NSA built SELinux to withstand attacks. The article shows us some of the relevant kernel architecture and compares SELinux to a few other approaches. We've discussed SELinux in the past. Quoting: "If you have a program that responds to socket requests but doesn't need to access the file system, then that program should be able to listen on a given socket but not have access to the file system. That way, if the program is exploited in some way, its access is explicitly minimized. This type of control is called mandatory access control (MAC). Another approach to controlling access is role-based access control (RBAC). In RBAC, permissions are provided based on roles that are granted by the security system. The concept of a role differs from that of a traditional group in that a group represents one or more users. A role can represent multiple users, but it also represents the permissions that a set of users can perform. SELinux adds both MAC and RBAC to the GNU/Linux operating system."&lt;p&gt;&lt;a href="http://linux.slashdot.org/article.pl?sid=08/05/11/1524236&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/1524236"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://linux.slashdot.org/article.pl?sid=08/05/11/1524236&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=N3gYfE"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=N3gYfE" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288124397" height="1" width="1"/&gt;</description>
<dc:creator>Soulskill</dc:creator>
<dc:date>2008-05-11T16:08:00+00:00</dc:date>
<dc:subject>security</dc:subject>
<slash:department>not-by-beating-the-end-boss-of-the-previous-level</slash:department>
<slash:section>linux</slash:section>
<slash:comments>161</slash:comments>
<slash:hit_parade>161,155,120,100,38,26,20</slash:hit_parade>
<feedburner:origLink>http://linux.slashdot.org/article.pl?sid=08/05/11/1524236&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://it.slashdot.org/article.pl?sid=08/05/11/1339228&amp;from=rss">
<title>The 25-Year-Old BSD Bug</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288103484/article.pl</link>
<description>sproketboy writes with news that a developer named Marc Balmer has recently fixed a bug in a bit of BSD code which is roughly 25 years old. In addition to the OSnews summary, you can read Balmer's comments and a technical description of the bug. "This code will not work as expected when seeking to the second entry of a block where the first has been deleted: seekdir() calls readdir() which happily skips the first entry (it has inode set to zero), and advance to the second entry. When the user now calls readdir() to read the directory entry to which he just seekdir()ed, he does not get the second entry but the third. Much to my surprise I not only found this problem in all other BSDs or BSD derived systems like Mac OS X, but also in very old BSD versions. I first checked 4.4BSD Lite 2, and Otto confirmed it is also in 4.2BSD. The bug has been around for roughly 25 years or more."&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/1339228&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/1339228"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/1339228&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=0qBC8j"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=0qBC8j" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288103484" height="1" width="1"/&gt;</description>
<dc:creator>Soulskill</dc:creator>
<dc:date>2008-05-11T15:05:00+00:00</dc:date>
<dc:subject>bug</dc:subject>
<slash:department>better-late-than-never</slash:department>
<slash:section>it</slash:section>
<slash:comments>209</slash:comments>
<slash:hit_parade>209,198,164,138,69,51,37</slash:hit_parade>
<feedburner:origLink>http://it.slashdot.org/article.pl?sid=08/05/11/1339228&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://tech.slashdot.org/article.pl?sid=08/05/11/120216&amp;from=rss">
<title>NSA Takes On West Point In Security Exercise</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288048326/article.pl</link>
<description>Wired is running a story about a recent security exercise in which the NSA attacked networks set up by various US military academies. The Army's network scored the highest, put together using Linux and FreeBSD by cadets at West Point. Quoting: "Even with a solid network design and passable software choices, there was an element of intuitiveness required to defend against the NSA, especially once it became clear the agency was using minor, and perhaps somewhat obvious, attacks to screen for sneakier, more serious ones. 'One of the challenges was when they see a scan, deciding if this is it, or if it's a cover,' says [instructor Eric] Dean. Spotting 'cover' attacks meant thinking like the NSA -- something Dean says the cadets did quite well. 'I was surprised at their creativity.' Legal limitations were a surprising obstacle to a realistic exercise. Ideally, the teams would be allowed to attack other schools' networks while also defending their own. But only the NSA, with its arsenal of waivers, loopholes, special authorizations (and heaven knows what else) is allowed to take down a U.S. network."&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/11/120216&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/120216"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/11/120216&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=5os5EB"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=5os5EB" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288048326" height="1" width="1"/&gt;</description>
<dc:creator>Soulskill</dc:creator>
<dc:date>2008-05-11T13:00:00+00:00</dc:date>
<dc:subject>military</dc:subject>
<slash:department>with-friends-like-these</slash:department>
<slash:section>tech</slash:section>
<slash:comments>137</slash:comments>
<slash:hit_parade>137,132,106,82,26,16,10</slash:hit_parade>
<feedburner:origLink>http://tech.slashdot.org/article.pl?sid=08/05/11/120216&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://it.slashdot.org/article.pl?sid=08/05/11/0327203&amp;from=rss">
<title>Spam Filtering For Small/Medium Business?</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/288023038/article.pl</link>
<description>or_is_it writes "The company I work for has been growing dramatically and I've been charged with the task of being the gatekeeper for our GFI Spam filters. This involves manually inspecting the subject line/to/from for all caught messages in each filter rule folder. For a company of about 50 people, in one day the number of spam messages can exceed 2,000. Neglect it for a day and you end up with quite a task on your hands. I've made the rules lax enough so important messages can go through, along with a few stray spams, for which I get bitched at. Tighten the rules up and then maybe an important time-sensitive email never gets to its intended recipient, and I get bitched at. Manually reading through all those subject lines is supposed to prevent that, but I'm only human and genuine messages can easily get overlooked. How do larger organizations deal with the spam issue? I can't imagine having one centralized person manually inspecting everyone's junk-mail header is the optimal solution. Purchasing a different commercial mail filter product is a possibility, but I'd like to hear some anecdotal evidence before jumping ship."&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/0327203&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/0327203"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/0327203&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=eQ3VGu"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=eQ3VGu" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/288023038" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-11T11:58:00+00:00</dc:date>
<dc:subject>spam</dc:subject>
<slash:department>dumpster-diving</slash:department>
<slash:section>it</slash:section>
<slash:comments>415</slash:comments>
<slash:hit_parade>415,414,303,157,35,21,8</slash:hit_parade>
<feedburner:origLink>http://it.slashdot.org/article.pl?sid=08/05/11/0327203&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://it.slashdot.org/article.pl?sid=08/05/11/014234&amp;from=rss">
<title>Gmail As Open-Relay Spam Server</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/287786460/article.pl</link>
<description>sveard writes of a little problem Google is having that has Gmail acting like an open relay. Compounding the issue is the fact that services such as Hotmail and Yahoo trust Gmail as a source of mail. "A recently-discovered flaw in Gmail is capable of turning Google's e-mail service into a highly effective spam machine. According to the Information Security Research Team (INSERT), Gmail is susceptible to a man-in-the-middle attack that allows a spammer to send thousands of bulk e-mails through Google's SMTP service without fear of detection. This attack bypasses both Google's identity fraud protection mechanisms and the current 500-address limit on bulk e-mail."&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/014234&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/11/014234"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/11/014234&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=rICLUq"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=rICLUq" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/287786460" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-11T01:14:00+00:00</dc:date>
<dc:subject>spam</dc:subject>
<slash:department>if-you're-not-part-of-the-solution-you're-part-of-the-precipitate</slash:department>
<slash:section>it</slash:section>
<slash:comments>143</slash:comments>
<slash:hit_parade>143,135,118,90,43,27,12</slash:hit_parade>
<feedburner:origLink>http://it.slashdot.org/article.pl?sid=08/05/11/014234&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://it.slashdot.org/article.pl?sid=08/05/09/164201&amp;from=rss">
<title>FBI Says Military Had Counterfeit Cisco Routers</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/286970578/article.pl</link>
<description>There are new developments in the case of the counterfeit Cisco routers, which we have been discussing for some time. The NYTimes updates the story after an FBI PowerPoint presentation made its way onto the Web. It seems that experts at Cisco have examined some of the counterfeit routers in detail and proclaimed that they contain no back doors. Others don't believe we can be so sure. "Last month, [DARPA] began distributing chips with hidden Trojan horse circuitry to military contractors who are participating in the agency's Trusted Integrated Circuits program. The goal is to test forensic techniques for finding hidden electronic trap doors, which can be maddeningly elusive... The threat was demonstrated in April when a team of computer scientists from the University of Illinois presented a paper at a technical conference in San Francisco detailing how they had modified a Sun Microsystems SPARC microprocessor... The researchers were able to create a stealth system that would allow them to automatically log in to a computer and steal passwords."&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/09/164201&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/09/164201"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://it.slashdot.org/article.pl?sid=08/05/09/164201&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=fnWkzQ"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=fnWkzQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/286970578" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-09T17:06:00+00:00</dc:date>
<dc:subject>security</dc:subject>
<slash:department>who-do-you-trust</slash:department>
<slash:section>it</slash:section>
<slash:comments>183</slash:comments>
<slash:hit_parade>183,178,140,104,34,22,17</slash:hit_parade>
<feedburner:origLink>http://it.slashdot.org/article.pl?sid=08/05/09/164201&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://tech.slashdot.org/article.pl?sid=08/05/09/1258229&amp;from=rss">
<title>Windows XP SP3 Creating Havoc</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/286839670/article.pl</link>
<description>ozmanjusri writes "According to Information Week, within hours of its wide availability Windows XP SP3 had drawn hundreds of complaints from users who claim the update is wreaking havoc on their computers. One user said in a Microsoft newsgroup: 'I downloaded and installed [the SP3] package for IT Professionals and Developers on one of my computers. Now I can't get the computer to boot. I don't think Microsoft should have made this a critical update.' Other sites including IT Wire are also reporting problems, which include include random reboots or the inability to boot at all." Note that XP3 won't install on systems running beta IE8; and after a successful SP3 install users will no longer be able to downgrade from IE7 to IE6.&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/09/1258229&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/09/1258229"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://tech.slashdot.org/article.pl?sid=08/05/09/1258229&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=bamjSt"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=bamjSt" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/286839670" height="1" width="1"/&gt;</description>
<dc:creator>kdawson</dc:creator>
<dc:date>2008-05-09T13:40:00+00:00</dc:date>
<dc:subject>windows</dc:subject>
<slash:department>shun-the-frumious-bandersnatch</slash:department>
<slash:section>tech</slash:section>
<slash:comments>739</slash:comments>
<slash:hit_parade>739,728,601,442,113,68,49</slash:hit_parade>
<feedburner:origLink>http://tech.slashdot.org/article.pl?sid=08/05/09/1258229&amp;from=rss</feedburner:origLink></item>

<item rdf:about="http://news.slashdot.org/article.pl?sid=08/05/08/2222254&amp;from=rss">
<title>Data Mining In Law Enforcement</title>
<link>http://rss.slashdot.org/~r/Slashdot/slashdotIt/~3/286414478/article.pl</link>
<description>jcatcw points out a blog entry by Scott McPherson, CIO for the Florida House of Representatives. McPherson condemns the state of data sharing and data mining in law enforcement, saying that the US causes itself a great deal of trouble by focusing more on "antiterror armor and nuke-sniffing devices" than a useful information distribution network. He discusses a few such projects, and how they could have directly affected the events of 9/11. Quoting: "One of those ingenious things that actually worked, Seisint founder Hank Asher's brilliant MATRIX system, remains mired in controversy and politics. Hank showed me MATRIX just a few short weeks after the 9/11 attacks. Using law enforcement data and commercial data, all of the commercial data available in the public domain, Asher's query produced [hijacker Mohamed] Atta's photo -- and about 80 others, many of them fellow 9/11 hijackers, many of them associates of the 9/11 hijackers. It was simple data mining and algorithms, and none of the information was obtained illegally."&lt;p&gt;&lt;a href="http://news.slashdot.org/article.pl?sid=08/05/08/2222254&amp;amp;from=rss"&gt;&lt;img src="http://it.slashdot.org/slashdot-it.pl?from=rss&amp;amp;op=image&amp;amp;style=h0&amp;amp;sid=08/05/08/2222254"&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://news.slashdot.org/article.pl?sid=08/05/08/2222254&amp;amp;from=rss"&gt;Read more of this story&lt;/a&gt; at Slashdot.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://rss.slashdot.org/~a/Slashdot/slashdotIt?a=RAfriJ"&gt;&lt;img src="http://rss.slashdot.org/~a/Slashdot/slashdotIt?i=RAfriJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://rss.slashdot.org/~r/Slashdot/slashdotIt/~4/286414478" height="1" width="1"/&gt;</description>
<dc:creator>Soulskill</dc:creator>
<dc:date>2008-05-08T23:05:00+00:00</dc:date>
<dc:subject>usa</dc:subject>
<slash:department>can't-they-just-google-it</slash:department>
<slash:section>news</slash:section>
<slash:comments>142</slash:comments>
<slash:hit_parade>142,136,108,84,29,19,10</slash:hit_parade>
<feedburner:origLink>http://news.slashdot.org/article.pl?sid=08/05/08/2222254&amp;from=rss</feedburner:origLink></item>

<textinput rdf:about="http://it.slashdot.org/search.pl">
<title>Search Slashdot</title>
<description>Search Slashdot stories</description>
<name>query</name>
<link>http://it.slashdot.org/search.pl</link>
</textinput>

</rdf:RDF>
