Doubts arise over fate of breathalyzer source code in Minn. case

TalkBack 14 of 14:

« Previous

• Thread View
• Flat View

Asine is that the code is hidden

the code vendor may fear that a competitor will take their future revenue with law enforcement. The code itself (if found to be bulletproof) will not help a drunk get off or a device be created to defeat the analyzer.

Think about that. The code is subject only to it's own strengths and flaws. No one is going to make a 'anti-radar' device for it, and if this analyzer employs any of the past improvements in breath measurement, chewing gum will not be outlawed as a get off tactic because it doesn't work, nor do pennies in your mouth, . . . and those things existed before this code.

So why hide the code in something so important as the device that can be a major part of a conviction and jail time . . . doesn't it stand bulletproof, . . . or does it put past convictions in question and vendor revenue at risk? And no, I'm not for drunk drivers (expecially habitual) getting off penalty free, but I'm not for possible false convictions and protecting those convictions to save face (govt).

Posted by: Boot_Agnostic   Posted on: 08/13/07 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now
• Email Security and Archiving - Clearer in the Cloud Google The time is NOW for businesses and organizations of all sizes to implement ... Download Now
• Can your business work smarter? IBM Today, productivity is at a premium and IT budgets are at a minimum. Work ... Download Now