OStatic

When a small Canadian company, i4i, recently won a $290 million judgment against Microsoft, much was made of the accompanying decree that Microsoft had 60 days to stop selling Microsoft Word in its current version. At issue were Custom XML-related patents that i4i defended. Microsoft has been very critical of the court's decision in the case, claiming that blocking the sale of Microsoft Word will also obstruct the sales of Microsoft Office, threatening industry. Microsoft is also set to appeal the court's decision on September 23rd.

Some in the open source community have interpreted the brouhaha as a big opportunity for open source software suites such as OpenOffice, and open standards such as Open Document Format (ODF). I'm in agreement with Andy Updegrove, though, who argues that the whole confrontation may be a tempest in a teapot.

There are many reasons to love the open source approach. The events chronicled in an article on NetworkWorld surrounding an exploit affecting Firefox outlines, quite elegantly, how open code outwardly appears risky, and -- well, wide open -- and how that same quality generates faster fixes and stronger applications.

A security researcher discovered that Firefox is vulnerable to remote memory corruption, enabling attackers to execute malicious (or at least very much unauthorized) code within the context of the browser. While security researchers spend countless hours searching out bugs and vulnerabilities, it's not usually the case that the offending attack finds its way into the public eye. Yesterday, however, this little exploit was published on several security sites. The vulnerability affects Firefox versions 3.0 through 3.0.7, on all platforms. In less than 24 hours, developers issued a patch for the vulnerability, to be included in next week's 3.0.8 release.