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
 
TRUST 2: Proliferation of COTS in Critical Infrast...
 
TRUST: Team for Research in Ubiquitous Secure Tech...
 
Bring us Your Metadata, Your Tired, Your Poor, You...
 
Building Blue Relationships and Partnerships
 
Secure Overlays on Insecure Internets: It Could Ha...
 
All Your BIOS Are Still Mine
 
CyLab's Angle on Sustainable Computing and Trustwo...
 
C# Moves Head in Statistical Leapfrog
 
Open Authentication: One-Time Passwords and Crypto...
 
Is Faith in Innovation Wearing Thin?

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

2005-04-21

 

FLINT for bug-free, secure, and reliable software.  That should cover it!

ACM News Service: Studies Recharge Computer Science.  Susie Poppick's 2005-04-20 Yale Daily News article recaps a number of activities in the Yale Computer Science Department. What caught my eye is the description of Zhong Shao's FLINT project.  I'm also a little wary of the blurb's use of "with an eye toward commercialization."  The article is clear that the project is oriented toward certification of commercially-marketed software.  That's reassuring although I don't think that's meant as a limitation. The FLINT approach involves writing certified software, accompanied by a logical proof (of what, pray tell?) that is amenable to mechanical verification.  I've always been curious how that could work, and I am more curious since it figures into my immediate interest in raising open-system trustworthiness. There are no links in the article, but a quick search provides some hot leads.  Of greatest importance is noticing that the methodology depends on use of a common intermediate language for expressing programs, and it is based on strong typing and safety qualities of the chosen intermediate form.  I know where I might be able to use that.  Some day. To dig into as part of my immediate trustworthiness preoccupations, there is FLINT's apparent use of SML/NJ (an open-source implementation of Standard ML, where ML is Robin Milner's Meta-Language), as well as efforts on secure programming and proof-carrying code to dig into.  The direction is interesting, though I am willing to start with code-carrying attestation, with code-carrying proofs a "nice-to-have when we can finally get it."

 
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 $