An Ongoing Lack Of Technical Prowess Is Resulting In Bad Laws, Bad Prosecutions, And Bad Judicial Decisions
from the ignorance-of-what-the-law-affects-is-the-perfect-excuse dept
Everyone in government is talking cyber-this and cyber-that, even though a majority of those talking don't have the technical background to back up their assertions. This leads to dangerous lawmaking. The CFAA, easily one of the most abused computer-related laws, came into being thanks to some skittish legislators who'd seen one too many 80's hacker films. ("WarGames," to be specific.)
Faulty analogies have led to other erroneous legislative conclusions -- like the comparison of email to snail mail -- which has led to the government treating any unopened email as "abandoned" and accessible without a warrant.
But the problem goes further than the legislative branch. The executive branch hasn't been much better in its grasp of technical issues, and the current slate of presidential candidates guarantees this won't change for at least another four years.
The judicial branch has its own issues. On both sides of the bench, there's very little technical knowledge. As more and more prosecutions become reliant on secretive, little-understood technical tools like cell tower spoofers, government-deployed malware, and electronic device searches, unaddressed problems will only multiply as tech deployment ramps up and infusions of fresh blood into the judicial system fail to keep pace.
Garrett M. Graff of Politico -- in a piece written for the Washington Post -- discusses how the government prosecutors' lack of tech expertise is resulting in bogus investigations and Constitutional violations.
Last year, the FBI nearly destroyed the life of an innocent physicist. In May 2015, agents arrested Xi Xiaoxing, the chairman of Temple University’s physics department, and charged that he was sneaking Chinese scientists details about a piece of restricted research equipment known as a “pocket heater.” An illustrious career seemed suddenly to implode. A few months later, though, the Justice Department dropped all the charges and made an embarrassing admission: It hadn’t actually understood Xi’s work. After defense experts examined his supposed “leaks,” they pointed out that what he’d shared with Chinese colleagues wasn’t a restricted engineering design but in fact a schematic for an altogether different type of device.
It's not just prosecutors. Graff notes that there's no "pipeline" of lawyers who can read and understand code heading to either side of prosecutions, which means defendants will be at the mercy of judges' interpretations of evidence and arguments. That's bad news as well.
As documents have surfaced thanks to the Snowden leaks and the government being more forthcoming with FISA court decisions, it's become apparent that judges issuing orders haven't been fully apprised of the technical details of the NSA's domestic surveillance programs.
The fallout from Edward Snowden’s revelations exposed numerous instances in which agency lawyers miscommunicated to courts about what the government was doing. There are two possible explanations: Either they willfully exploited judges’ lack of technical knowledge, or the lawyers themselves couldn’t fathom the programs they were trying to explain.
Irritated FISC judges have come down hard on the agency periodically, pointing out serious misrepresentations by the NSA's lawyers. Unfortunately, these discoveries have always come well after the fact. In the periods between judicial benchslaps, the agency has acted with autonomy. Forgiveness is better than permission, especially when the person approving surveillance requests either doesn't have all the information they need or is unable to interpret the information they've been provided.
The lack of expertise -- and the lack of new talent flowing in -- means this sort of thing will continue to happen far too often. Judges will be duped. Defendants will end up jailed because of the ignorance surrounding them. Bad analogies will shore up inadequate explanations. And, if you're the sort who believes "accused" means "guilty," the shortage of knowledgeable prosecutors will result in jaw-dropping "technicalities" returning suspected criminals to the streets.
In one recent prosecution of a security researcher accused of illegal hacking, an assistant U.S. attorney summarized the case to the court by saying, “He had to download the entire iOS system on his computer, he had to decrypt it, he had to do all of these things I don’t even understand.” The government ultimately lost the case.
So, what can be done to fix it? Not much. Only a few law schools offer classes in cybersecurity, coding, or other tech fields. Those that do have long waiting lists. The upside is that a technically-proficient law school grad should find plenty of opportunities awaiting them. The downside is that there's not nearly as much money in the public sector as there is in the private. This may mean criminal defense will see a boost in knowledge, but that will only help those who can afford to hire top-tier lawyers.
The government, meanwhile, will likely continue to stumble over its own ignorance. Fortunately for government prosecutors, most judges are willing to cut government prosecutors a lot of slack, something only exacerbated by lawmakers pushing legislation targeting things they don't even understand.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: expertise, law, policy, politics, technology
Reader Comments
Subscribe: RSS
View by: Time | Thread
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
(I mean, yeah, he's said some fairly dumb things, but I think most of those were intended as jokes. Like, when he said he was going to use social engineering to get into the San Bernardino shooter's phone -- obviously a joke, but the media reported it as if he'd been serious.)
I used to think that, as my generation got older and became lawmakers, lawyers, and judges, that would lead to a better understanding of technology among the people making, enforcing, and interpreting the laws.
Then I went to work at a university computer store. After a few months dealing, on a more-than-daily basis, with college-aged customers who didn't know the difference between Windows and Office, it became quite clear to me that most people my age don't understand computers any better than my grandparents do.
[ link to this | view in chronology ]
Sergey Aleynikov, case in point.
According to wikipedia a new law was added to make his actions illegal, even if they still do not understand what happened. Trade secrets cannot involve foss. And they simply cannot understand that.
The current mindset of our government is punish any that they want to. Regardless of the facts.
Add to that the basis of his work is/was math which cannot be protected.
[ link to this | view in chronology ]
Re: Sergey Aleynikov, case in point.
Never let facts get in the way of a good prosecution.
[ link to this | view in chronology ]
A matter of priorities
[ link to this | view in chronology ]
It seems that stupidity *is* an excuse...
Bunch of hypocrites.
[ link to this | view in chronology ]
Ridiculous patent
Dear Uncle Sam: Way to Streisand!
[ link to this | view in chronology ]
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Wargames
The government creates a piece of technology that its own users (the US Air Force) does not actually understand. When it functions in a way that wasn't intended, every solution the government proposes won't work:
- Unplug it
- Just tell it to stop
- Explain to this machine the difference between reality and a game
And the solution that actually fixes the problem is a 100% technical solution borne from an understanding of the actual technology itself:
(spoiler...)
- Make it play tic-tac-toe against itself to teach it futility.
It really is a microcasm of what's wrong with the government interfering with technology that it doesn't understand - and why technical solutions, not legal ones, are the only options that actually work, and why you need technical people, not congressmen, to invent and implement them.
Of course, then they can't campaign on the "success" of their law to "protect the children" on the "big bad internet" (mostly form themselves rather than any actual danger...) while conveniently omitting that their magical law totally broke the internet itself.
[ link to this | view in chronology ]
Re: Wargames
[ link to this | view in chronology ]
Re: Wargames counting down.
The thing that is really funny is Ronnie The Ray Gun bought this hook line and sinker. One wonders if the Air Force used pass codes that worked like in the movie.
[ link to this | view in chronology ]
Re: Re: Wargames
People often forget how brute force code cracking actually works (or usually just don't know in the first place.) The odds that the code would actually be the very LAST code that it tried are nearly 0%. But it would've been a very strange sense of dramatic tension for the movie if it was humming along, trying 10k attempts/second, and when it got around 5% through, boom, it has the code. Even though in a technically accurate movie, that's WAY more likely to happen (the code began with a C, so since it's a cipher with only upper case letters and numbers, it's about 5% into the potential codes table.)
All that said, my point was simply to illustrate that Wargames, even if perhaps unintentionally, is actually a very apt analogy for why the government should stay the hell out of the technology space unless or until they get people in government who actually understand the technology they're legislating about (i.e. the point of the article.) Wargames is like a cautionary tale of what could very well happen (and on a non-nuclear scale, HAS happened) when the government just expects technology people to "nerd harder" while passing laws that often make any attempt to do so illegal (anti-reverse-engineering clause anyone?)
[ link to this | view in chronology ]
Re: Re: Re: Wargames
Actually, the odds that the code would be the very last code that they tried are about 100%. Why would you keep trying after you have found the code? It's like how your keys are always found in the last place that you looked. It has a 100% probability because if you cease an activity after achieving your goal of finding something, then there is a 100% probability that the last place you look will have the item you're searching for.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
The Cyber Is To Important Too Be Left To The Cyberers
Cant do it? Maybe your using TERRORIST MATH!!!
Your trying to keep a Cabal. Well, WERE GOING TO CUT THE CABAL!!!!
[ link to this | view in chronology ]
Re: The Cyber Is To Important Too Be Left To The Cyberers
:)
[ link to this | view in chronology ]
So, nu?
A.k.a., "representative democracy."
[ link to this | view in chronology ]
well
I'll quote what my darling spouse has said online in numerous occasions (it explains EVERYTHING)
"Have you met people?"
[ link to this | view in chronology ]
Re: well
[ link to this | view in chronology ]
[ link to this | view in chronology ]