MN Supreme Court Backs Reasoned Requests For Breathalyzer Source Code
viralMeme writes with news that the Minnesota Supreme Court has upheld the right of drunk-driving defendants to request the source code for the breathalyzer machines used as evidence against them, but only when the defendant provides sufficient arguments to suggest that a review of the code may have an impact on the case. In short: no fishing expeditions. The ruling involves two such requests (PDF), one of which we've been covering for some time. In that case, the defendant, Dale Underdahl simply argued that to challenge the validity of the charges, he had to "go after the testing method itself." The Supreme Court says this was not sufficient. Meanwhile, the other defendant, Timothy Brunner, "submitted a memorandum and nine exhibits to support his request for the source code," which included testimony from a computer science professor about the usefulness of source code in finding voting machine defects, and a report about a similar case in New Jersey where defects were found in the breathalyzer's source code. This was enough for the Supreme Court to acknowledge that an examination of the code could "relate to Brunner's guilt or innocence."
I'd hate to see Slashdot supporting these wreckless drunks just because they claim to be l33t haX0rs.
Does this mean that if a defendant presents a copy of Bruner's exhibits, he's likely to get the go-ahead in that state?
Bruce Perens.
So essentially challenging evidence gathering methods is insufficient, but making colorful posters and waving around a PhD is fine?
Slashdot has way to much code running on the main page, my laptop's scroll can't keep up and goes bonkers.
Frist Pwst!
but, seriously, this is an important step, for a person's rights, and ultimately, toward our collective safety ... it's a necessary evil to be subjected to this type of testing, so at least let's get it right oto prevent false positives ...
I assume breathalyzer evidence is given such great weight because it is "scientific evidence"? Then why shouldn't be subject to peer review... which is a central tenet of science? Without that, it's nothing more than a magical "black box, of unknown accuracy, and does not deserve to be considered "scientific proof"... throw away part of the valid process of science, and you debase the source of its supposed objectivity.
Do what thou wilt shall be the whole of the Law
He could still be found guilty of DUI assuming other evidence was convincing; and for that matter, they could still cart people to a hospital for a blood test.
I'm glad that the courts allowed the defendant to view the source code (or at least get it analyzed). Software is not without its defects. It's my belief that any software that is used by the government to convict any of its citizens should be open for public review.
Now, the fact that he had to persuade the judge to allow the source code to be examined is upsetting but I think overall, its a positive move.
"Slashdot still works with javascript disabled."
Sort of.
For example, without Javascript and running Index2, you cannot delete messages from the system - all the delete anchors are of the form '<a href="#" onclick="stuff">' and so are useless.
And if you aren't running index2, you don't get notifications of responses and the like anymore - at least that has been my experience.
www.eFax.com are spammers
Thought I would share this, and before a bunch of you start posting BS about the claim of who wrote what, that is not the point. The point is the evolution of MN DWI law and technology.
My father as a prosecutor in Minneapolis in the 60's and 70's started prosecuting drunk drivers for things like felony manslaughter and such. At the time it was just misdemeanor, and often the police would just give someone a ride home. The State legislators and several lobby groups caught wind of it and asked him to write the laws. Those became the first felony laws for DWI in MN, and later where used as a model for other States around the country. Obviously they have been super modified since then, but the fundamental principle that DWI is something serious is still there.
My father went on in private practice as defense attorney in the 80's. Almost all of his acquittals on DWI came down to discrediting the probable cause (i.e. the officer) for the arrest in the first place. Typically the officer's judgment was always front and center (e.g. did he really see him cross the center line on an ice covered road). It got progressively harder as they started adding video cameras and other technology to get someone off on a DWI charge, as the officer's judgment became less important.
I suspect since my father's time, the only thing left to really attack is the validity of the technology itself that measures the crime.
Living in Chile
Will the same thing also be for red light cameras / speed cameras / video toll systems and more?
If I get red light ticket should I ask for the light timing tables? the camera timing tables? When the last time the light was tested as well testing the camera system? how it is tied into the light part of the main controller or is it a add on to the controller. Was the railroad system working right if it is a light with a railroad crossing part of it?
There have been cases for yellow times being to short for speed limit of the road and tickets have to be voided and some times the cameras triggering on yellow.
You may end up getting a red light ticket from a quick green to red at a light with a railroad crossing at it. Then if that where me I would want to have the logs and setting for all parts of the light like The pre-emptive / interconnected rail gates to light settings / The light timing settings / mini clear time / time be telling the camera system that the light is red after turning red / yellow time / camera system wait time and other times as well. Maybe even the code but like just the timings and how things are linked will do in that case.
I don't like the idea of a cheap hack like hooking to red light power bus other then a link to the cpu / data bus / network bus that interconnected rail / lights liked to other lights use.
I actually really like the idea that the court system is allowing defendants to view the source code of the breathalyzer. In today's time drunk driving is a very serious offense that could affect the rest of a person's life if convicted. It would be wrong to convict a person of drunk driving if there was an error in the way the breathalyzer was functioning.
Just as one can't prove a negative
Not this crap again...
http://www.google.com/#hl=en&q=can't+prove+a+negative
"When information is power, privacy is freedom" - Jah-Wren Ryel
At least not in any jurisdiction I'm aware of, but you can demand one. This is the way to go too, have them take blood, and demand a sample be taken for your attorney as well. The reason is that the only way to accurately measure blood alcohol content is to, well, measure the amount of alcohol in the blood.
The reason the breathalyzer manufacturers are so scared to have their units inspected isn't because there's something evil in the source, but because they know it is a flawed system. They are things that can be accurate, but only if the assumptions they make are correct, and they aren't for all people. As such you can't guarantee an accurate result. If this gets widely shown in court, well then their devices are likely to lose use with law enforcement.
More or less their method for measuring BAC could be compared to measuring the current running through a circuit by measuring the intensity of the light bulb on that circuit. Such a thing can work and give accurate results, but only if you make correct assumptions. You need to know the efficiency of the bulb, the voltage of the circuit, and if there is resistance anywhere else in there. So if your system was designed for incandescent bulbs but your were measuring a florescent, you'd get the wrong result. Same deal if you were designed for a 120v line and it was a 240v bulb.
This is why the breathalyzer companies have flat out refused to hand over their source in various cases. They know that their market is going to vastly shrink if they do.
So as I said: Always demand a blood sample, and another for your lawyer so it can be independently tested. This, of course, won't do any good if you are actually driving drunk but my advice in that situation is don't. However it will do a good job of keeping you from falsely being charged/convicted.
I'm afraid you're joking to the lawn with this one.
I hate to see slashdoters ignoring the basic principles of our justice system just to pursue some prejudice against accused drunk drivers.
I think enough of us who are older have known people to be killed by drunk drivers and I honestly have no idea why drunk drivers are even allowed to live after they kill someone.
Drunk driving is not an accident. Killing someone DUI should be MURDER TWO.
There, that's my prejudice.
The bottom line is, if someone is getting pulled over for DUI, its because they were already obviously driving smashed. You can see them when you drive - weaving, going slow, forgot to put the headlights on, maybe stopping too soon or too often... and for what? Really, for what do people do this?
This is my sig.
I think enough of us who are older have known people to be killed by drunk drivers and I honestly have no idea why drunk drivers are even allowed to live after they kill someone.
So go kill the drunks that killed your friends. Be the vigilante.
Or allow that due process of law should trump personal feelings in these matters.
The bottom line is, if someone is getting pulled over for DUI, its because they were already obviously driving smashed.
People drive poorly for all sorts of reasons apart from intoxication. Being tired, or distracted, or suffering from a condition that causes poor night vision all too frequently lead to accidents.
And not everyone who gets pulled over is guilty of something. Cops make mistakes too...
"Slashdot still works with javascript disabled."
Sort of.
For example, without Javascript and running Index2, you cannot delete messages from the system - all the delete anchors are of the form '<a href="#" onclick="stuff">' and so are useless.
And if you aren't running index2, you don't get notifications of responses and the like anymore - at least that has been my experience.
Just allow slashdot.org, not the other stuff. Comments clicks nicely expand the thread without a full redraw and cut off.
Treading water in North Africa (deep in de Nile). Simply not drinking and driving avoids such unpleasant circumstances. After all those years, I'm actually happy, joyous, and free not to do that anymore. Good luck, and don't kill my kids, please.
Keep Doing Good.
That thing is a black box. Blow goes in and a number comes out. The State fights attempts to determine what happens in between.
This is good news. Get yourself a software expert (IF YOU'RE DAMN RICH), then evaluate the software.
Way to go Minnesota.
This is going to be a field day for experts ($). The States had better timely respond to this!!
Breath test machines are a fantastic use of open source software. Transparency.
This is HUGE its gonna spread and it's going to really affect lots of things, especially time for trial timelines.
This is going to be the new DWI defense lawyer fad.
Wouldn't YOU be pissed if you knew you weren't drunk
If I knew I weren't drunk, how could I be pissed (i.e. drunk)?
From one of the links .. (SysTest being the company hired by the Breathalyzer company to review the source code and Base One being the company hired by the accused)
> SysTest only looked for "mal-ware", not for functioning of the code.
>
> Base One, however, did an extensive evaluation, finding 19,400 potential errors in the code.
How can you find "mal-ware" when you don't consider the purpose of the code.
And here is their algorithm to average n = 4 readings ... "When the software takes a series of readings, it first averages the first two readings. Then, it averages the third reading with the average just computed. Then the fourth reading is averaged with the new average ... which would cause the first reading to have more weight ... Nonetheless, the comments say that the values should be averaged, and they are not."
Even if they get the source code for the program, they now have a valid reason to also ask for the source code to the compiler - as this may also have bugs.
In fact, if the program or compiler have had ANY revisions due to bug fixes, then one could argue that the current version of either also could have bugs.
I agree with getting the exact source code of a product in use to support a claim. That professor that got code for the voting machine however is a criminal. He obtained the code illegally, and that company did not prosecute him.
You can't settle criminal cases easily
In which country? In the United States, most criminal defendants settle with a guilty plea to a lesser charge rather than let the matter go to a jury.
What the MN supreme court said is that you cant just say "I want to look at the code because there might, possibly, be something wrong with it", you have to give some idea of *what* you think might be wrong with it.
I think the algorithm that the device uses to translate signals from a silica sensor into an estimate of blood alcohol has flaws. A relevant one is failure to correct for alcohol in the mouth but not in the bloodstream, such as recent drinking, recent use of mouthwash, or belching. Other problems with breath alcohol measurement in general include failure to correct for hematocrit, failure to correct for breathing pattern, failure to correct for temperature, failure to remind the user to recalibrate against a control, and failure to correct for ketones common in the breath of people with diabetes and low-carb dieters.
If you drink, don't drive. Period.
gee... who'ld've thunk it...
Don't drink and drive.
Don't drink, then drive.
If you drink, lose your keys.
I for one, like the idea of this.
Have you had a drink tonight?
just 1 beer.
Thank you, you're license has beenr revoked for life, and your car will be crushed into a cube and planted in your front yard. Have a nice day!