Blunder Dome Sighting  
privacy 
 
 
 

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.



Click for Blog Feed
Blog Feed

Recent Items
 
Uh Oh: Time to Refresh Java
 
Open Source: Shrinking the Trust Surface
 
Open-Source: How Trustworthy, How Secure?
 
Trustworthy Software Security: How Do We Get There...
 
Zombie Planet: Spam and Phish Egg Harvesting
 
Lost in Twisty Overlays All the Same: Peer Pressur...
 
To Engineer is to Tinker?
 
A Feed Too Far
 
Security is a Programming Problem?
 
Ending the Madness: Deja Triple Vu

This page is powered by Blogger. Isn't yours?
  

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

2004-11-08

 

How SCO Changed Our Awareness

eWeek: Does SCO Matter?.  This 2004-11-03 article by Steven J. Vaughan-Nichols summarizes how badly SCO is doing in its choices to pursue claims of Unix IP and contract violations. The part that I find interesting is that the lawsuits have made corporate purchasers of software keenly aware of lurking IP and provenance issues in the software that it acquires (or licenses).  There are links to two companies that wouldn't exist had this not happened: OSRM and Black Duck Software. OSRM is in the seminar and insurance business, but there is a section of their offerings on best practices that needs further investigation. Black Duck Software is a bit more straightforward, providing compliance management support, and the confirmation of IP and related issues seems to be in their ballpark.  Although focus appears to be on companies that develop their own software using third-party and open-source components, it would seem that there is something that open-source developers could do to make this easier.  I am interested in trustworthiness arrangements for open-source, and one important aspect of trustworthiness is that something be legally safe to use, not merely secure. I'll be following up on these.

 
Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $