<?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>keeping simple &#187; security+fault-tolerance</title>
	<atom:link href="http://www.yodaiken.com/category/software-engineering/securityfault-tolerance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yodaiken.com</link>
	<description>Systems software technology and business</description>
	<lastBuildDate>Sun, 01 Jan 2012 18:30:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Droning on about computer security</title>
		<link>http://www.yodaiken.com/2011/10/1207/</link>
		<comments>http://www.yodaiken.com/2011/10/1207/#comments</comments>
		<pubDate>Sat, 08 Oct 2011 20:05:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software security]]></category>
		<category><![CDATA[computer security]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=1207</guid>
		<description><![CDATA[Good grief. The US military&#8217;s unmanned Predator and Reaper drones are continuing to fly remote missions overseas despite a computer virus that has infected their US-based cockpits. Government officials are still investigating whether the virus is benign, and how it &#8230; <a href="http://www.yodaiken.com/2011/10/1207/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Good grief.</p>
<blockquote><p>The US military&#8217;s unmanned Predator and Reaper drones are continuing to fly remote missions overseas despite a computer virus that has infected their US-based cockpits.<br />
Government officials are still investigating whether the virus is benign, and how it managed to infect the heavily protected computer systems at Creech Air Force Base in Nevada, where US military pilots remotely fly the planes on their missions over Iraq, Afghanistan and elsewhere.<br />
&#8220;Something is going on, but it has not had any impact on the missions overseas,&#8221; said a source, who was not authorized to speak publicly.<br />
Armed tactical unmanned planes have become an increasingly valuable tool used by the US military to track and attack individuals and small groups overseas, but the virus underscores the vulnerability of such systems to attacks on the computer networks used to fly them from great distances.<br />
Rob Densmore, former US navy airman, told Al Jazeera that the infection was a common keystroke logging virus &#8211; which registers the keystrokes pilots use to control the unmanned drones from afar.<br />
&#8220;It has to have a point of access, so we know that thumb drives &#8211; basically USB drives &#8211; are used to upload navigational information, guidance information to Predator and Reaper drones.<br />
&#8220;And if there&#8217;s a way somehow that that information, or that thumb drive, can come into contact with a network or with the internet, that&#8217;s where the danger is because that basically means that information can be carried across from the Reaper drones.&#8221;</p>
<p><a href="http://english.aljazeera.net/news/americas/2011/10/201110816388104988.html" onclick="pageTracker._trackPageview('/outgoing/english.aljazeera.net/news/americas/2011/10/201110816388104988.html?referer=');">http://english.aljazeera.net/news/americas/2011/10/201110816388104988.html</a></p></blockquote>
<p>Government approach to security can be described as designing an unsinkable boat that has no doors between compartments and then, to make it usable, cutting a random and increasing number of undocumented holes between compartments.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2011/10/1207/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Boeing security</title>
		<link>http://www.yodaiken.com/2011/05/boeing-security/</link>
		<comments>http://www.yodaiken.com/2011/05/boeing-security/#comments</comments>
		<pubDate>Sat, 07 May 2011 18:54:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[software security]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=1159</guid>
		<description><![CDATA[So the court said Matthew Neumann and Nicholas Tides were properly fired in 2008 for violating company policy of disclosing company information to the media, in this case the Seattle Post-Intelligencer, without company authorization. In 2007, the PI wrote: “Boeing and &#8230; <a href="http://www.yodaiken.com/2011/05/boeing-security/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<blockquote><p>So the court said Matthew Neumann and Nicholas Tides were properly fired in 2008 for violating company policy of disclosing company information to the media, in this case the <em>Seattle Post-Intelligencer</em>, without company authorization.</p>
<p>In 2007, the PI wrote: “<a href="http://gflorencescott.wordpress.com/2008/05/10/computer-security-faults-put-boeing-at-risk/" onclick="pageTracker._trackPageview('/outgoing/gflorencescott.wordpress.com/2008/05/10/computer-security-faults-put-boeing-at-risk/?referer=');">Boeing and its external auditors</a> have rated the company’s inability to patch database and software development security holes as a ’significant deficiency’ with the computer infrastructure since 2004 — the first year it had to comply with the 2002 law. The failure has been deemed serious enough that for three years in a row, finance teams have spent the last 45 days of each year testing whether financial numbers are correct.</p>
<p>from <a href="http://www.wired.com/threatlevel/2011/05/whistleblower-firings/" onclick="pageTracker._trackPageview('/outgoing/www.wired.com/threatlevel/2011/05/whistleblower-firings/?referer=');">Wired</a>.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2011/05/boeing-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wikileaks</title>
		<link>http://www.yodaiken.com/2010/11/wikileaks/</link>
		<comments>http://www.yodaiken.com/2010/11/wikileaks/#comments</comments>
		<pubDate>Tue, 30 Nov 2010 02:42:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software security]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=1122</guid>
		<description><![CDATA[Most of the diplomatic messages released by Wikileaks have been traced to a US defence department network, known as Siprnet, used for the exchange of classified information, media reports say. [..] It is thought about 2.5 million US military and &#8230; <a href="http://www.yodaiken.com/2010/11/wikileaks/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<blockquote><p>Most of the diplomatic messages released by Wikileaks have been traced to a US defence department network, known as <a href="http://www.yodaiken.com/wp-content/uploads/2010/11/clouseau.jpg"><img class="alignleft size-full wp-image-1124" title="clouseau" src="http://www.yodaiken.com/wp-content/uploads/2010/11/clouseau.jpg" alt="" width="225" height="225" /></a>Siprnet, used for the exchange of classified information, media reports say.</p>
<p>[..]</p>
<p>It is thought about 2.5 million US military and civilian personnel have access to the network.</p>
<p>However, Siprnet is not recommended for distribution of top-secret information.</p>
<p>Siprnet uses the same technology as the internet, but has dedicated and encrypted lines that are separate from all other communications systems, according to a defence department users&#8217; guide.</p>
<p>The system is protected by a series of security measures, the guide adds:</p>
<ul>
<li>All users must be approved and registered</li>
<li>Passwords are complex, and must be changed every 150 days</li>
<li>Only accessible from specially enabled computers in secure location</li>
<li>Computers must not be left unattended</li>
<li>No linking to civilian internet without prior approval</li>
<li>Media storage devices become classified at secret level once connected to Siprnet-enabled computers</li>
<li>Audit trail of all users, including identity of all persons accessing Siprnet</li>
</ul>
<p>However, the guide says that technological advances in storage devices have made it easier to remove classified information from secure areas [...]</p>
<p>It is alleged that an online security system to detect suspicious use of Siprnet was switched off on computers used by the US military in Iraq following complaints that it was inconvenient, the UK&#8217;s Guardian newspaper reports.</p>
<p>.<a href="http://www.bbc.co.uk/news/world-us-canada-11863618" onclick="pageTracker._trackPageview('/outgoing/www.bbc.co.uk/news/world-us-canada-11863618?referer=');"> http://www.bbc.co.uk/news/world-us-canada-11863618</a></p></blockquote>
<p>So you release data to 2,500,000 human beings scattered around the world and are surprised when your (expensive and annoying) security measures don&#8217;t work.</p>
<p>Oh.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2010/11/wikileaks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Airbus computer and electrical problems</title>
		<link>http://www.yodaiken.com/2010/11/airbus-computer-and-electrical-problems/</link>
		<comments>http://www.yodaiken.com/2010/11/airbus-computer-and-electrical-problems/#comments</comments>
		<pubDate>Sat, 13 Nov 2010 01:53:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[embedded systems]]></category>
		<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=1097</guid>
		<description><![CDATA[Whoops! From Aviation Week According to a bulletin issued by the U.K. Air Accidents Investigation Branch (AAIB), an electrical fault led to a series of display and control problems. These included the intermittent failure of both pilots’ electronic displays and &#8230; <a href="http://www.yodaiken.com/2010/11/airbus-computer-and-electrical-problems/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Whoops! From <a href="http://www.aviationweek.com/aw/generic/story_channel.jsp?channel=mro&amp;id=news/awx/2010/11/12/awx_11_12_2010_p0-269169.xml&amp;headline=A321%20Control%20Issues%20Prompt%20Fault%20Warning" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.aviationweek.com/aw/generic/story_channel.jsp?channel=mro_amp_id=news/awx/2010/11/12/awx_11_12_2010_p0-269169.xml_amp_headline=A321_20Control_20Issues_20Prompt_20Fault_20Warning&amp;referer=');">Aviation Week</a></p>
<blockquote><p><img class="alignleft size-full wp-image-1098" title="biggles-hodder-06" src="http://www.yodaiken.com/wp-content/uploads/2010/11/biggles-hodder-06.jpg" alt="" width="170" height="233" /></p>
<p>According to a bulletin issued by the U.K. Air Accidents Investigation Branch (AAIB), an electrical fault led to a series of display and control problems. These included the intermittent failure of both pilots’ electronic displays and the uncommanded application of left rudder trim.  [..] The crew also reported hearing “chattering” from the circuit breaker panels.  During the incident the crew flew the A321 manually, referring to the standby instruments which continued tofunction normally.  The problem was rectified after the crew switched off the No. 1 generator in response to an ‘ELEC GEN 1 FAULT’ message on the Airbus’s ECAM warning display, says the AAIB.  The cause has been traced to an electrical problem and the AAIB says that<span style="text-decoration: underline;"><span style="color: #ff0000;"> Airbus indicates that a reset of the Flight Augmentation Computer, caused by an electrical power interruption, can result in incremental offsets in rudder trim.</span></span></p></blockquote>
<p><span style="text-decoration: underline;"><span style="color: #ff0000;"><br />
</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2010/11/airbus-computer-and-electrical-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>parallel processing and bash reduce</title>
		<link>http://www.yodaiken.com/2009/07/parallel-processing-and-bash-reduce/</link>
		<comments>http://www.yodaiken.com/2009/07/parallel-processing-and-bash-reduce/#comments</comments>
		<pubDate>Thu, 23 Jul 2009 23:00:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[data center]]></category>
		<category><![CDATA[operating systems]]></category>
		<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[map reduce]]></category>
		<category><![CDATA[parallel computing]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=498</guid>
		<description><![CDATA[It&#8217;s sad that after all this time, one can look at any random article on parallel programming and find some variation of: for i = 1 ... n create thread i do something end for as if that was the &#8230; <a href="http://www.yodaiken.com/2009/07/parallel-processing-and-bash-reduce/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s sad that after all this time, one can look at any random article on parallel programming and find some variation of:</p>
<pre>for i = 1 ... n
      create thread i
             do something
end for</pre>
<p>as if that was the only way to express parallel computation. This is such an awkward way of looking at problems.Â  I think many problems come from the sloppy &#8220;non-determinism&#8221; of the operating systems and multi-core machines.Â  One of the fewÂ  interesting ideas seen in the last 20 years on parallel processing is the Google <a title="google map reduce" href="http://labs.google.com/papers/mapreduce.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/labs.google.com/papers/mapreduce.html?referer=');">map-reduce scheme</a> ( . But what I find impressive is <a title="bash reduce" href="http://github.com/erikfrey/bashreduce/blob/71619384b2ab07ff61443a4ca54591b03c44dce0/br" target="_blank" onclick="pageTracker._trackPageview('/outgoing/github.com/erikfrey/bashreduce/blob/71619384b2ab07ff61443a4ca54591b03c44dce0/br?referer=');">bashreduce.</a> This is really a clever trick and a great validation of the UNIX toolset design (as if it needed another validation).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2009/07/parallel-processing-and-bash-reduce/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Power Systems Reliability Challenges</title>
		<link>http://www.yodaiken.com/2009/04/power-systems-reliability-challenges/</link>
		<comments>http://www.yodaiken.com/2009/04/power-systems-reliability-challenges/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 23:42:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[communications]]></category>
		<category><![CDATA[green power]]></category>
		<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[electric power]]></category>
		<category><![CDATA[fire ants]]></category>
		<category><![CDATA[system reliability]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=256</guid>
		<description><![CDATA[It is becoming more common for fire ants to build nests in pad mounted equipment. Their nesting materials can cause short circuits, the ants can eat away at conductor insulation, and they make equipment maintenance a challenge. from Power System &#8230; <a href="http://www.yodaiken.com/2009/04/power-systems-reliability-challenges/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<blockquote><p><em>It is becoming more common for fire ants to build nests in pad moun<a href="http://www.yodaiken.com/wp-content/uploads/2009/04/fire-ant300.jpg"><img class="size-medium wp-image-257 alignright" title="fire-ant300" src="http://www.yodaiken.com/wp-content/uploads/2009/04/fire-ant300.jpg" alt="fire ant" width="270" height="179" /></a>ted equipment. Their nesting materials can cause short circuits, the ants can eat away at conductor insulation, and they make equipment maintenance a challenge.</em></p>
<p>from Power System Reliability, by Richard Brown, in the Electric Power Engineering Handbook</p></blockquote>
<p>The subdued poetry of engineering documents &#8220;<span style="text-decoration: underline;">and they make equipment maintenance a challenge</span>&#8220;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2009/04/power-systems-reliability-challenges/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Marine One Blueprints via Pirates Bay</title>
		<link>http://www.yodaiken.com/2009/03/marine-one-blueprints-via-pirates-bay/</link>
		<comments>http://www.yodaiken.com/2009/03/marine-one-blueprints-via-pirates-bay/#comments</comments>
		<pubDate>Mon, 02 Mar 2009 05:32:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[communications]]></category>
		<category><![CDATA[real-time]]></category>
		<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software security]]></category>
		<category><![CDATA[computer security]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=240</guid>
		<description><![CDATA[Goodness. The US blueprints for Marine1 show up in Iran. &#8220;What appears to be a defense contractor in Bethesda, Md., had a file-sharing program on one of their systems that also contained highly sensitive blueprints for Marine One,&#8221; Boback said. &#8230; <a href="http://www.yodaiken.com/2009/03/marine-one-blueprints-via-pirates-bay/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Goodness. The US blueprints for Marine1 <a title="MSNBC story" href="http://www.msnbc.msn.com/id/29447088/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.msnbc.msn.com/id/29447088/?referer=');">show up</a> in Iran.</p>
<blockquote><p>&#8220;What appears to be a defense contractor in Bethesda, Md., had a file-sharing program on one of their systems that also contained highly sensitive blueprints for Marine One,&#8221; Boback said.</p>
<p class="textBodyBlack">Tiversa also found sensitive financial information about the cost of the helicopter on that same computer, WPXI-TV reported.</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2009/03/marine-one-blueprints-via-pirates-bay/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mobile device security and President Obama</title>
		<link>http://www.yodaiken.com/2009/01/mobile-device-security-and-president-obama/</link>
		<comments>http://www.yodaiken.com/2009/01/mobile-device-security-and-president-obama/#comments</comments>
		<pubDate>Thu, 22 Jan 2009 17:41:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software security]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=215</guid>
		<description><![CDATA[Obama&#8217;s fighting hard to keep his Blackberry President Barack Obama will have a beloved BlackBerry â€” and maybe a second, more secure smartphone-like device â€” with him in the White House. The president has been adamant about continuing to use &#8230; <a href="http://www.yodaiken.com/2009/01/mobile-device-security-and-president-obama/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Obama&#8217;s fighting hard to keep his Blackberry</p>
<blockquote><p>President Barack Obama will have a beloved BlackBerry â€” and maybe a second, more secure smartphone-like device â€” with him in the White House.</p>
<p class="textBodyBlack">The president has been adamant about continuing to use a BlackBerry, a smartphone with Internet and <a class="iAs" style="border-bottom: 0.075em solid darkgreen ! important; font-weight: normal ! important; font-size: 100% ! important; text-decoration: underline ! important; padding-bottom: 1px ! important; color: darkgreen ! important; background-color: transparent ! important;" href="http://www.msnbc.msn.com/id/28780205/#" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.msnbc.msn.com/id/28780205/?referer=');">e-mail access</a>, despite concerns that are likely making the National Security Agency as nervous as the Secret Service on Inauguration Day when Obama left his presidential limo twice to walk and wave to crowds along Pennsylvania Avenue. <a title="MSNBC article on Obama's phone" href="http://www.msnbc.msn.com/id/28780205/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.msnbc.msn.com/id/28780205/?referer=');">MSNBC</a></p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2009/01/mobile-device-security-and-president-obama/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Great software patents: fault tolerance</title>
		<link>http://www.yodaiken.com/2009/01/great-software-patents-fault-tolerance/</link>
		<comments>http://www.yodaiken.com/2009/01/great-software-patents-fault-tolerance/#comments</comments>
		<pubDate>Sun, 04 Jan 2009 22:12:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[architecture]]></category>
		<category><![CDATA[auragen]]></category>
		<category><![CDATA[data center]]></category>
		<category><![CDATA[intellectual property]]></category>
		<category><![CDATA[security+fault-tolerance]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=204</guid>
		<description><![CDATA[software patent <a href="http://www.yodaiken.com/2009/01/great-software-patents-fault-tolerance/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<blockquote><p>A parallel computer system which has a primary task processor, a second      primary task processor, a secondary task processor acting as a backup for      the second primary task processor transfers messages by: sending messages from the primary task processor to the second primary      processor with the second primary task processor operating on the messages      by initially storing a received message in a queue and thereafter reading      the message from the queue for processing in accordance with the task      associated therewith and accumulating a count of the messages read from      its queue; and sending the same messages from the first primary task      processor to the secondary task processor which stores the messages in a      message queue for possible use if the second primary task processor fails.      If a primary task processor fails after processing a given number of      messages, the secondary task processor associated therewith starts      processing the messages in its queue but after having discarded the first      given number of messages.</p></blockquote>
<table border="0" width="100%">
<tbody>
<tr>
<td width="10%" align="left" valign="top">Inventors:</td>
<td width="90%" align="left"><strong><a name="h3" href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&amp;Sect2=HITOFF&amp;u=%2Fnetahtml%2FPTO%2Fsearch-adv.htm&amp;r=1&amp;f=G&amp;l=50&amp;d=PTXT&amp;p=1&amp;p=1&amp;S1=%28glazer.INNM.+AND+fault%29&amp;OS=IN/glazer+and+fault&amp;RS=%28IN/glazer+AND+fault%29#h2" onclick="pageTracker._trackPageview('/outgoing/patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2_amp_Sect2=HITOFF_amp_u=_2Fnetahtml_2FPTO_2Fsearch-adv.htm_amp_r=1_amp_f=G_amp_l=50_amp_d=PTXT_amp_p=1_amp_p=1_amp_S1=_28glazer.INNM.+AND+fault_29_amp_OS=IN/glazer+and+fault_amp_RS=_28IN/glazer+AND+fault_29_h2&amp;referer=');"></a><strong><em>Glazer</em></strong>; Sam D.</strong> (New York, NY)<strong>, Baumbach; James</strong> (Brooklyn, NY)<strong>, Borg; Anita</strong> (New York, NY)<strong>, Wittels; Emanuel</strong> (Englewood Cliffs, NJ)</td>
</tr>
<tr>
<td width="10%" align="left" valign="top">Assignee:</td>
<td width="90%" align="left"><strong>Parallel Computers Systems, Inc.</strong> (Fort Lee,  NJ)</td>
</tr>
<tr>
<td width="10%" align="left" valign="top">Appl. No.:</td>
<td width="90%" align="left"><strong> 06/443,937</strong></td>
</tr>
<tr>
<td width="10%" align="left" valign="top">Filed:</td>
<td width="90%" align="left"><strong>November 23, 1982</strong></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2009/01/great-software-patents-fault-tolerance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updated Dijkstra vs Perlis (really, DeMillo)</title>
		<link>http://www.yodaiken.com/2008/11/updated-dijkstra-vs-perlis-really-demillo/</link>
		<comments>http://www.yodaiken.com/2008/11/updated-dijkstra-vs-perlis-really-demillo/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 14:09:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[architecture]]></category>
		<category><![CDATA[security+fault-tolerance]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[software security]]></category>
		<category><![CDATA[dijkstra]]></category>
		<category><![CDATA[formal methods]]></category>
		<category><![CDATA[verification]]></category>

		<guid isPermaLink="false">http://www.yodaiken.com/?p=183</guid>
		<description><![CDATA[See below.]]></description>
			<content:encoded><![CDATA[<p>See <a href="http://www.yodaiken.com/2008/11/dijkstra-versus-perlisdijkstra-versus-perlis/" target="_self">below</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.yodaiken.com/2008/11/updated-dijkstra-vs-perlis-really-demillo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

