Senate Not Concerned About How Often NSA Spies On Americans, But Very Concerned That It Built Open Source Software To Do So
from the priorities,-people dept
Wired has a troubling story of how the Senate Armed Services Committee is pushing a bill that would likely kill off an open source NoSQL project that came out of the NSA called Accumulo. Like many other such NoSQL efforts, the NSA basically took some Google white papers about its BigTable distributed database setup, and built its own open source version, with a few improvements... and then open sourced the whole thing and put it under the Apache Foundation. It's kind of rare to see such a secretive agency like the NSA open source anything, but it does seem like the kind of thing that ought to be encouraged.Unfortunately, the Senate Armed Services Committee sees things very differently. As part of a 600-page bill that's being floated, it actually calls out Accumulo by name, and suggests that it violates a policy that says the government shouldn't build its own software when there are other competing commercial offerings on the market. The reasoning is basically that the government shouldn't spend resources reinventing the wheel if it can spend fewer resources using existing code. You can see the basic reasoning behind that, but applying it here makes little sense. As the article notes, here we're talking about software that's already been developed and released -- not a new effort to rebuild existing software. In fact, those who follow this stuff closely note that Accumulo did "break new ground" with some of its features when it was being built. To then kill it afterwards seems not just counterproductive, but could also create a chilling effect for government open source efforts, which seem like something we should be encouraging, not killing.
What's really odd is the close interest that the Senate seems to be paying to this. The discussion is very specific, naming Accumulo and some of the competing offerings on the market. They're specifically calling out this one product. Of course, as Julian Sanchez notes, there's a bit of irony in the fact that the very same Senate appears to have absolutely no interest in finding out how often the NSA spies on Americans... but sure is concerned about what database it uses to store all of the information it's getting.
Of course... all of this raises a separate issue in my mind: can the NSA even open source Accumulo? I though that creations of the federal government were automatically public domain, rather than under copyright. And, thus, putting it under a specific license might, in fact, present limitations that the government can't actually impose on the software.... Thus, shouldn't the software code actually be completely open as a public domain project? The government should be able set up an Apache-like setup, but one without any restrictions on the code.
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: accumulo, bigtable, databases, nosql, nsa, open source, senate, spying
Reader Comments
Subscribe: RSS
View by: Time | Thread
It's a distinction that will probably end up in favor of the NSA actually, since they undoubtedly made a product with features that weren't offered in a commercial product and would have been expensive to contract a commercial entity to add.
[ link to this | view in chronology ]
The Real Problem With Open Source Spy Software
[ link to this | view in chronology ]
Re: The Real Problem With Open Source Spy Software
[ link to this | view in chronology ]
Re: Re: The Real Problem With Open Source Spy Software
[ link to this | view in chronology ]
Re: Re: Re: The Real Problem With Open Source Spy Software
[ link to this | view in chronology ]
Re: Re: Re: Re: The Real Problem With Open Source Spy Software
There is so much superfluous data and information going through their systems it really doesn't matter if they have your personal information. Nobody else but the NSA can see what they have collected without an order from the CIA.
I think it's safe to say congress is just worried that they aren't "stimulating" the economy by spending away the federal budget (or lack thereof).
[ link to this | view in chronology ]
I get this a lot
My personal theory is that no government agency wants to save money since it means they'll have to do without the difference for the next budget cycle. I've heard stories of tens of thousands of dollars being spent on useless software just to ensure that the agency in question would be able to maintain their budget.
[ link to this | view in chronology ]
Re: I get this a lot
I think a more sensible and reasonable solution would be to keep the unused portion of the budget as a credit to the agency/department (up to a limit and/or to an amount that finances a bigger project) for posterior use.
Wishful thinking. People sometimes are quick to point the waste of taxpaying money but they aren't aware of the bureaucracy hell inside Governmental bodies that end up forcing all sorts of inefficiency.
[ link to this | view in chronology ]
Re: Re: I get this a lot
The effect of budget reviewers saying your are asking How Much!! for this change??? is simple. Budget authors pad the request and require the purchasing agents in the department to make sure the entire request is used, preferably with a little bit of a budget overrun that can be used to justify "We failed to ask for enough last time...give us a raise to cover our expected needs"
Actually planning and requesting one time funding for a project is a nightmare as there is no history for the budget committee to look at and see that the request is not unusual. Unusual in the eyes of the bureaucratic bean counter is almost identical to unnecessary.
[ link to this | view in chronology ]
Contrary to popular opinion, Americans are not the world's dumbest people...
[ link to this | view in chronology ]
Re: Contrary to popular opinion, Americans are not the world's dumbest people...
[ link to this | view in chronology ]
Re: Re: Contrary to popular opinion, Americans are not the world's dumbest people...
[ link to this | view in chronology ]
Fine then
Any changes they made could be akin to doing performance tweaking/testing with any other product.
[ link to this | view in chronology ]
Re: Fine then
[ link to this | view in chronology ]
I'm reminded of a book . . .
[ link to this | view in chronology ]
Re: I'm reminded of a book . . .
[ link to this | view in chronology ]
Re: Re: I'm reminded of a book . . .
[ link to this | view in chronology ]
Spending
Senate (publicly): We want to know how many people you've spied on Americans.
NSA: You don't have the security clearence or the brain power to know what is actually done.
Senate (privately): How dare you not SPEND money to create jobs.
Given the current US economy, the fact that the NSA used open source programming languages to do any spying makes a lot of sense. Under the GNU, you have to distribute it for free if you release the code to the public. Since they haven't released the code to the public, I see no problem with that. They saved their department a lot of money and made us slightly less dependent on the government. Well you know how spending alone creates debt....and that's why our debt ceieling is so high.
[ link to this | view in chronology ]
Re: Spending
[ link to this | view in chronology ]
Re: Re: Spending
* "open source programming languages" -- who said anything about programming languages? This is open-source software.
* "Under the GNU" -- It's the Apache License, not the GPL (if that's what you meant to refer to)
* "you have to distribute it for free if you release the code to the public" -- You have deeply misunderstood the GPL. It's the other way around. Sort of. And the GPL places no burden on the original author, only on licensees.
[ link to this | view in chronology ]
What Restrictions does the Apache License place on code?
What restrictions does the Apache License place upon the code?
The license, as I understand it; says one can do anything to the code. You can modify it; extend it, sell it, create your own version without any restrictions, release it under a different license, etc...
I'm surprised at how open the Apache license is.
[ link to this | view in chronology ]
Re: What Restrictions does the Apache License place on code?
It makes sense to put it out as a licensed managed project, rather than simply posting the source & docs on a website and saying "This is public domain, take it or leave it".
The managed project will gather outside improvements that are then available for the classified internal version of NoSQL.
[ link to this | view in chronology ]
Re: Re: What Restrictions does the Apache License place on code?
[ link to this | view in chronology ]
Re: Re: What Restrictions does the Apache License place on code?
[ link to this | view in chronology ]
Re: Re: Re: What Restrictions does the Apache License place on code?
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re: Time To Dig
Dig a little deeper.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re: Disclosure
They follow it quite well. People tend to forget that human beings actually work at the NSA unlike congess, where we have a bunch of howler monkies trying to gain power for their side alone. I kind of wish congess would see we are human as the NSA does.
[ link to this | view in chronology ]
I will
Now, if only we could do that with the Congress.
Open source. Open media. Open government.
If you do not subscribe to at least two of the above, in whole or in part, then you might be part of a rather sizable problem.
As for prioritizing the "issue" of software selection over one of the very tenets of this fucking country... fuck you you worthless pieces of shit.
[ link to this | view in chronology ]
Precisely what we do for you and people around the world :-)
[ link to this | view in chronology ]
federal government works
Depends on how you define "creations of the federal government". Works that are created by federal employees can not be copyrighted, but works directed by federal employees, but actually done by contractors can be copyrighted. (more info) It is not who pays for it, it is who actually does the writing that counts. I couldn't tell from the article whether contractors were used or not.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Government Copyright
If the government actually built it with government employees then it would be public domain in terms of copyright law but it might still be restricted from release to the general public (in context think trade secret rather than patent).
Different parts can be under different restrictions. So, even if the project is open source, any changes done by the government may still be restricted or otherwise withheld from the general public. The government can, at that point, still license the software under those restrictions.
Of course, if someone stuck those changes in a public git repository (in an official capacity) then it seems moot, but that's why we have so many lawyers.
[ link to this | view in chronology ]