8 ms·
Bill requiring US agencies to share source code with each other becomes law
- jmclnx 2y agoA worthwhile law, but I have been there many times in the corporate world with various departments required to do the same. Just saying it (passing a law) will not make it happen, it will require a lot of work on everyone's part. I wish them luck.
- deleted 2y ago[deleted]
- rc_kas 2y agoWow. Some rare good news from the US government.
- 93po 2y agounless this is just an easy money grab for billions in contractors, with senators who own the businesses, to work as hard as possible at non-compliance
- JumpCrisscross 2y agoYes, a thing is not a thing if it’s something entirely different.
- Mountain_Skies 2y agoOr AI companies looking for more LLM feed material.
- Dalewyn 2y agoGenerally speaking, anything and everything paid for with taxpayer dollars should be made public. Public Monies Public Goods should be the absolute basis.
- sigzero 2y agoDisagree with that in the case of software.
- AdamJacobMuller 2y agoWhy?
- tracer4201 2y agoWhat is the downside? I was thinking it could compromise software security, although my layman understanding is we’re better off if the open source community finds and makes problems visible? Or there are other software secrets that we wouldn’t want state adversaries to see, like things that block your access under export control laws?
- deleted 2y ago[deleted]
- fortyseven 2y agoYou provide a convincing argument. My mind is changed.
- drewcoo 2y agoSo everything from classified material to office memos and personnel records? That's not gonna happen. If you, at home, pay someone to do work, what exactly do you own beyond the end product?
- chii 2y agosome slippery slope arguments are stupid, such as yours. Obviously you keep personnel records private (unless there's some law/court case requiring it be open). Classified material is already classified, and is kept private regardless - but there's a good argument to be made that there ought to be automatic declassification of material after a set amount of time (perhaps 20-30 years). Declassifying material is good for the public, as the ability to audit the past prevents future abuses.
- coopreme 2y agoGood intentions but I don’t expect much to come except contractor 1’s would-be competitors closing the gap or using this to throw stones based on existing contract code quality. It is easier to write code than it is to read code!!
- timschmidt 2y ago> I don’t expect much to come except contractor 1’s would-be competitors closing the gap That means increased competition and reduced costs for the government. > or using this to throw stones based on existing contract code quality That means code review, which results in improved code quality one way or another. I fail to see the problem here.
- coopreme 2y agoThat’s cool. These are my expectations. Company 1 wins contract and builds something, key team members are experienced with making and navigating the “process”. Company 2 copy/pastes. They have not performed any work yet but they entered a bid X years later and bring up the years of “mediocre” dev Company 1 has done. There is only existing company 1 work and only hope of company 2. Contracting Officer chooses company 2 because promises sound good! Reality, company 2 wins on cost and doesn’t understand the context of what was built or the environment it was built in. They don’t understand the costs as they didn’t pay them. Company 2 quickly proposes “full rewrite!” Lower cost labor they brought in can’t perform and quality degrades till we have (insert Gov software program here). Or it doesn’t happen.
- angled 2y agoIdeally, a body such as NIST would become the stewards of federal libraries that contractors are then compelled to use and improve. If the end goal is about cost efficiency more than any other ideal or objective, then that type of centralisation and reuse should be promoted and enforced.
- timschmidt 2y agoOrganizations often make a few missteps before figuring out what works. Some amount of failure is to be expected when doing anything on the scale of a nation. At least if everything's open, each attempt has the opportunity to learn from the last and can be evaluated on it's merits in comparison. It's also likely that other organizations will find some of the software useful.
- jasonlfunk 2y agoIt’s hard to know what they hope to accomplish with this bill. Anytime you develop custom code, it’s because you need something, well, custom. What are the chances that something custom built for one agency is going to be at all useful to the custom needs of another agency?
- monetus 2y agoYou would think some "glue code" around their databases could maybe be shared, or eventually converge. How they handle forms? Something.
- chii 2y agoby arguing the need to be sharing code (despite it not being the logical thing to do), you end up with (sub)contractors who will have more work to do to comply, and to make an otherwise simple system more complex by virtue of having to shove two separate systems together in one, so that they could be shared between agencies!
- JumpCrisscross 2y ago> by virtue of having to shove two separate systems together in one, so that they could be shared between agencies Where does the bill require interoperability?
- Terr_ 2y agoI think you're confusing share (make available) with share (mandatory reuse).
- dgrin91 2y agoAlmost 100%. Most 'custom code' I've written in my career for various employers, customers, clients, etc has been very similar. Business logic tends to be <10%, the rest is just integrating stuff and piping data.
- deleted 2y ago[deleted]
- 2y ago
- anonymousiam 2y agoThis would have been useful to me 10 years ago when I was trying to get my hands on Ghidra within channels.
- greyface- 2y ago4(a)(1)(B) NATIONAL SECURITY.—An exemption from the requirements under section 3 shall apply to classified source code or source code developed—[...](ii) by an agency, or part of an agency, that is an element of the intelligence community (as defined in section 3(4) of the National Security Act of 1947 (50 U.S.C. 3003(4)). https://www.congress.gov/bill/118th-congress/house-bill/9566/text#H79DE6B72D7694B518DB34DD9AA409F03 https://www.congress.gov/bill/118th-congress/house-bill/9566...
- hermannj314 2y agoWhat's the cynical scam angle for this bill? If agencies share code, there will be a need for coordination of changes, someone makes extra money in the process? i.e. a small contractor doesn't get the change request because only some big player can handle the complexity of a mutli-agency contract? The government is full of cronies, this bill was passed because someone has plans to use it to screw us all over.
- somenameforme 2y agoI'd expect some tech guys in one branch wanted access to some relevant/useable code from another branch, the other branch refused for whatever reason, and we get bickering that eventually makes its way up.
- smcin 2y agoAny informed specilation on which branch wanted to use which branch's code?
- smitty1110 2y agoRead section 4 of the law, especially the automatic exemptions. Lots of stuff isn't covered.
- hermannj314 2y agoI have read section four. How does it connect with my comment? I'm not sure what an automatic exemption is? I speculated this bill may feel good, but like all things in the government, was only passed because wealthy cronies have determined it is a net good for them in the long run. What connection am I missing?
- thebigspacefuck 2y agoI’ve heard some contractors intentionally license source code they provide in a way that it can’t be reused and if it can only if they provide it to you again, so the government basically pays for the same code over and over. Even if it’s highly reusable. Maybe this will help with that?
- jtaft 2y agoHow does this affect exploits?
- potato3732842 2y agoThat's my first thought. The NSA and CIA probably have all sorts of in-house developed source for all sorts of evil things that they sure won't be sharing.
- cmg 2y agoFrom the article: > The new law doesn’t apply to classified code, national security systems or code that would post privacy risks if shared.
- maxloh 2y agoThat sounds like a security nightmare. A single accidental exploit in one agency could easily spread to others reusing the same code. Now, imagine if that exploit was instead intentionally planted by a foreign spy, targeting common use cases...
- treyd 2y agoThis is just another form of the "security through obscurity" argument used against foss in general. Many eyes make all bugs shallow.
- throwup238 2y ago> Under the law, agency chief information officers are required to develop policies within 180 days of enactment that implement the act. Those policies need to ensure that custom-developed code aligns with best practices, establish a process for making the metadata for custom code publicly available, and outline a standardized reporting process. > Per the new law, metadata includes information about whether custom code was developed under a contract or shared in a repository, the contract number, and a hyperlink to the repository where the code was shared. Sadly it doesn't sound like the law requires agencies to make the code publicly open source, it just requires inter-agency sharing (bill full text [1]). They only need to share "metadata" publicly. [1] https://www.congress.gov/bill/118th-congress/house-bill/9566/text https://www.congress.gov/bill/118th-congress/house-bill/9566...
- throwaway314155 2y agoI feel like the posted headline makes that sufficiently clear.
- userbinator 2y agoI get suspicious any time the word "best practices" appears, because it's likely to just encourage more bureaucratic cargo-culting.
- vegetablepotpie 2y agoI mean, it’s not like we’ve ever seen this with the agile movement /s. I’ve gone through “agile transitions” in government contracting, at a high level it starts out with a high concept idea of reducing lead times and increasing productivity. Then directives get handed down through layers of management, the decision is made to adopt Scrum or SAFe™, that gets handed down to middle management, who tailor the process in ways that specifically benefit themselves, and you end up with waterfall done poorly and with extra steps™. What will happen is that there will be very loose definitions of source code and flexible definitions timing when code is released. If an agency does not want to share, they’ll find a way to evade, and still check off the box.
- johndhi 2y agoI expect secrets to be shared in that code and data breaches to follow (not that they wouldn't anyhow...)
- Frummy 2y agoAwesome. I remember the pain of not even being able to read code within one and the same organisation, stuff like this I imagine will make work easier for anyone who builds top-down mental models.
- yieldcrv 2y agoDeloitte in shambles
- dgrin91 2y agoI wonder how this works for defense/law enforcement agencies. Do they get some special carveout?
- mlindner 2y agoThat's stated in the article.
- pigbearpig 2y ago> The new law doesn’t apply to classified code, national security systems or code that would post privacy risks if shared. Seems pretty clear they would.
- dgrin91 2y agoAh, thanks! Missed that.
- PaulWaldman 2y agoThis article references "custom code." What about custom applications? Are all government contractors required to provide the source code for all developed applications? Or does this bill only apply to contracts where the deliverables actually include source code?
- deleted 2y ago[deleted]
- transpute 2y agoU.S. DoD has an FAQ on open-source software, http://dodcio.defense.gov/OpenSourceSoftwareFAQ.aspx http://dodcio.defense.gov/OpenSourceSoftwareFAQ.aspx & https://github.com/risacher/DoD-OSS-FAQ https://github.com/risacher/DoD-OSS-FAQ > This version is being posted to GitHub as an experiment in collaborative tools for public engagement of government policy documents. Suggestions for changes or additions to this document by military or civilian personnel, contractors, and private citizens may be submitted as pull requests.. (2010) https://www.youtube.com/watch?v=WWt0YiXcEkE https://www.youtube.com/watch?v=WWt0YiXcEkE Dan Risacher, from the DoD CIO's office, and open source security expert David A. Wheeler break down the history and ramifications of the recent DoD memo, which makes clear the Department of Defense's stance that open source is a viable, commercial form of software. (2024) https://openssf.org/press-release/2024/10/29/openssf-expands-secure-development-course-with-interactive-labs/ https://openssf.org/press-release/2024/10/29/openssf-expands... [Linux Foundation] OpenSSF recognizes the need for security education.. said David A. Wheeler, director, open source supply chain security at OpenSSF..Since its inception, more than 25,000 individuals have enrolled in this course material.
- doubleorseven 2y agoThis is great. In my country agencies use code as trade like "i will give you the code to generate holograms to by pass video KYC and you will give me men power to spread fake news". Because there is no sharing, agencies spend a lot of money developing multiple versions of the same need, not all with great success. This bill should take you further in terms of quality and advantage.
- m463 2y ago> ...collaborative software companies Atlassian and GitLab Inc. backed the legislation. lol :)
- somenameforme 2y ago"The new law doesn’t apply to classified code, national security systems or code that would post (sik) privacy risks if shared." What sort of code would pose privacy risks if shared? That sounds like some nasty intermixing of code and data.
- bigstrat2003 2y ago> "The new law doesn’t apply to classified code, national security systems or code that would post (sik) privacy risks if shared." Ironically, it's "sic", not "sik". Muphry's Law got you when you weren't looking. ;)
- Dalewyn 2y ago>Muphry's Law EDIT: TIL this is a law of its own. Happy New Year!
- treetalker 2y agoMuphry's Law: "If you write anything criticizing editing or proofreading, there will be a fault of some kind in what you have written." https://en.wikipedia.org/wiki/Muphry's_law https://en.wikipedia.org/wiki/Muphry's_law
- franga2000 2y agoNo real risks, but this gives them a convenient excuse not to. I've had companies and government agencies refuse FOIA requests for technical documentation on privacy grounds because "it applies to a system that processes personal information", with some adding that "knowing the inner-workings of the system would lead to a likely compromise of the system". Yes, government contractors will gladly admit between the lines that their code is garbage and they largely rely on security through obscurity. And the information comissioner has agreed with them a few times!
- Xen9 2y agoThere's no difference between the two.
- kube-system 2y ago
- lifeisstillgood 2y agoSo I tried (!) campaigning for a full OSS model (https://web.archive.org/web/20200920095030/http://oss4gov.org/manifesto https://web.archive.org/web/20200920095030/http://oss4gov.or...) based on the idea that public money means public shoukd see what comes from the money. To me the default for any government software should be OSS unless ministerially signed off. But I was young and naive
- toomuchtodo 2y ago> But I was young and naive Just ahead of your time. Progress is both a grind and a marathon.
- input_sh 2y agoFSFE shares your opinion across the pond: https://publiccode.eu/en/ https://publiccode.eu/en/
- badgersnake 2y agoI don’t think that’s so controversial, neither does the UK government - https://www.gov.uk/service-manual/technology/making-source-code-open-and-reusable https://www.gov.uk/service-manual/technology/making-source-c...
- lifeisstillgood 2y agoThis was starting sometime in 2010, as gov.uk was gearing up IIRR, plus most people you talked to at the time in local government would just stare and not have a clue about open source. We have honestly come a very long way (I reckon we do a “generation” each decade - making me a third time around ) However - as always, we have not come Far enough
- calebh 2y agoI've worked at military contractor jobs for years, and there are many people there who believe this - if the taxpayer is paying and the software isn't classified, then it should be open source. Ghidra is a great example of this, and having this software be free has been of great benefit to the security community.
- _kb 2y agoThis is great. I’ve spent some time working with gov teams where this is recommended practice [0]. In many cases though codifying as a requirement is still needed for that recommendation to be followed. This is particularly true for those who have not been part of OSS community before, which is common in public service. As others have highlighted, public funds should lead to public good and open source is a great way to increase that benefit. [0]: https://www.forgov.qld.gov.au/information-and-communication-technology/qgea-directions-and-guidance/qgea-policies-standards-and-guidelines/digital-service-standard/make-source-code-open-by-default https://www.forgov.qld.gov.au/information-and-communication-...
- briandear 2y agoCouldn’t source code be requested under FOIA? It’s technically a government document.
- ibigb 2y agoYes it can; I've done this in the past.
- austin-cheney 2y agoFor those of you with no government experience I suspect you have absolutely no idea why this is so challenging. The military is allergic to internal software. First of all you have to understand IT in the military is a different world far beyond your imagination because everyday they are under attack by the best nation-state cyber intrusion people on the planet. Your start up will never experience this and the mega corp, like Facebook will only just barely experience anything like this because it’s just not that important. The only commercial organizations that even come remotely close to what the military experiences daily are large financial organizations. Also, don’t forget the US military is the largest single employer on the planet, like 4.5 Walmarts. So the military monitors everything at multiple levels. That also means locking things down to approved software lists at different levels. The people writing the security policies and/or performing the monitoring likely aren’t experienced software directors. They look at things like NPM and Maven and just see unlimited attack vectors from people who have no idea about security, and they aren’t wrong. Then in the civilian and contractor space where do you put the code. If it’s paid for by the government then it’s owned by the government otherwise the contractor company wants to own it completely separated from the government so they can charge the government for it. Then consider if it’s a subcontractor not aligned to the financial goals of the prime contractor. Even when the government wants to do the right thing it’s complicated. As a software guy under a non managing co-prime I really don’t give a shit and say just give the government everything and it’s weird to see people try to throw up layers, especially since the government side is always less restricted because they almost always achieve vastly superior security accreditation on their infrastructure.
- anshumankmr 2y ago>They look at things like NPM and Maven and just see unlimited attack vectors from people who have no idea about security, and they aren’t wrong. Then what do they do? Aren't there tools to check for security vulnerabilities in the market like Sonar Qube? Wouldn't (or couldn't) the millitary run a beefed up version of that and developers can't check in code without ensuring 100% compliance to security vulnerabilities
- NegativeK 2y ago
- sylware 2y agoWell, it will allow code inspection by some agencies... but the "re-use", forget about it.
- Dowwie 2y agoSharing source code isn't enough. The right people need to be aware of its existence at the right time. For instance, there needs be part of their governance that due diligence be performed prior to executing a contract.
- openthc 2y agoWe create open-source software and attempt to get government agencies to adopt/use it. It's crazy how alergic these agencies are to open-source. Some will even create their own, with legacy style implementations (csv uploads, broken parsers), complete with bugs/flaws that are predicatble rather than use someone elses code. When responding to RFPs, the open-source stuff has an a higher level of scrutinty than the closed systems. Like, if it's open then you have to show it's good but if it's closed the vendor just says "yep, we are perfect" and the agency could move on. It feels like the agency, and the employees don't want any responsibility. But I've never seen anyone lose their government job from some incompetence.
- georgeplusplus 2y ago>>>It's crazy how allergic these agencies are to open-source. It’s about job protectionism on the greater scale and being the subject matter expert who leverages his code base for promotions on the individual scale. generally agencies do not view each other as working for the same team. It can be very competitive when lobbying for resources from congress for your agency. I work in gov and speaking from first hand knowledge. The culture is toxic. It’s broken and I can’t wait to see what changes Elon and trumps team propose.
- taskforcegemini 2y agohopefully a different approach than with twitter
- stronglikedan 2y agoYou can't hold anyone accountable for open source. With closed source, there's someone else to point the finger at when things go wrong.
- doublepg23 2y agoI heard this a lot before I started my career but IME this rarely pans out and you’re just stuck with broken software without documentation and source code.
- ThinkBeat 2y agoImagine all the interesting code that will come from the NSA.
- sunbum 2y agoSomeone didn't read the link.
- droideqa 2y agoI was really sad when people sued the NSA over developing Accumulo[0]. [0]: https://www.techdirt.com/2012/07/18/senate-not-concerned-about-how-often-nsa-spies-americans-very-concerned-that-it-built-open-source-software-to-do-so/ https://www.techdirt.com/2012/07/18/senate-not-concerned-abo...
- idontwantthis 2y agoAny idea what the definition of "source code" is? I'm wondering if low-code workflows would count.
- vaadu 2y agoDoes it apply to the FBI, NSA and CIA?
- gosub100 2y agoI would like to see this go further. Have publicly funded universities develop "enterprise" government software such as DMV or other agencies, completely FOSS, and each year have a public hearing where the CEOs of the private contractors that currently provide this software can explain why, exactly, the FOSS version isn't good enough to replace theirs.