Live data from Hacker News

Public Money, Public Code

publiccode.eu

81–90 of 216 posts

Re: Public Money, Public Code

#81

Question for HN: How could this possibly work with software developed for the military?

Kerckhoff-Shannon principle. Unless I can assume that my enemy has total access to knowledge of my mechanisms, but is in no way advantaged with respect to my operations, it is not an effective weapon.

Re: Public Money, Public Code

#82

Why do software developers always shoot themselves in the foot with regard to their economic value? Governments pay all the time for development of technology that they buy, but that doesn't mean that the IP is released. For example, the government paid Boeing to develop transport aircraft. However, that does not mean that all the drawings/plans/etc for the aircraft are made public. The government is buying a set of…

IIRC they actually can demand copies of the drawings/plans for their own records and use so that they can dig them up if the B-52 needs to be extended another decade.

Governments are better at keeping ancient records around than most companies.

Re: Public Money, Public Code

#83

The state I lived in developed one of those covid tracking apps. I asked for the source code and was told it wasn't available and would never be. I talked to people working on other software developed for the state and they all think that software shouldn't be public. It seems crazy to me that taxpayers pay for this software but it doesn't belong to them. Knowing what I do know I gotta wonder if it's just about those…

I was tangentially related to the covid app stuff so I can offer some insight there: most of those apps weren't built by the state. Google provided an open-source "base app" that could be customized by the states, but most states hired third-party contractors to build an app for them. I've worked in public sector and this is typical. the states can't open source it because they don't own it, they just pay a third-par…

[deleted]

Re: Public Money, Public Code

#84

The state I lived in developed one of those covid tracking apps. I asked for the source code and was told it wasn't available and would never be. I talked to people working on other software developed for the state and they all think that software shouldn't be public. It seems crazy to me that taxpayers pay for this software but it doesn't belong to them. Knowing what I do know I gotta wonder if it's just about those…

This is the kind of issue that causes all that government bloat... If I was a state employee and I wrote the app, and I had to release the source code, then I'm making it very easy for a bad actor to find a vulnerability and exploit it to leak the data of citizens. One might respond: "Well software shouldn't have those holes! Just because it's closed source, doesn't mean that won't happen anyway Also true, in an idea…

> However security by obscurity is a layer of defense...

In your example it would be the layer of defense. But then we still have to wonder who is the attacker? The assumption made on the web page is that the developer is the attacker. The obscurity then becomes a major issue rather than the defense.

Yes, we will have to pay what it costs and we will have to add extra developers. We all know the difference?

I could write any government app or software but it would be a slow process, it would be hostile to further development and the security of it would be laughable. But from the GUI you wouldn't notice the difference. Mine might actually be nicer.

Re: Public Money, Public Code

#85
post #78
post #76

Earlier quoted context omitted.

How so? Because of external contributors? Most software developed for the public sector is quite use-case specific (and the use-cases are often quite boring), so I don’t see that happening for most projects.

Over time the use-cases will grow, and if done right you'll start being able to "borrow" from similar use-cases in other areas/governments. It WOULD likely require massive retooling as much "government code" is more like "black box machine that does X" than "fancy new web-app".

In my experience, that doesn’t happen much even between projects within a single software company, because requirements are too diverse and change too frequently. Pushing for synergies also tends to create all sorts of internal political dynamics. At best it’s a long shot, with high risk of not amortizing the cost. The rest of the world, including the open-source world, also isn’t a promising role model, with the constant churn, fragmentation and evolution of languages, frameworks, libraries and tooling.

Re: Public Money, Public Code

#86

The state I lived in developed one of those covid tracking apps. I asked for the source code and was told it wasn't available and would never be. I talked to people working on other software developed for the state and they all think that software shouldn't be public. It seems crazy to me that taxpayers pay for this software but it doesn't belong to them. Knowing what I do know I gotta wonder if it's just about those…

This is the kind of issue that causes all that government bloat... If I was a state employee and I wrote the app, and I had to release the source code, then I'm making it very easy for a bad actor to find a vulnerability and exploit it to leak the data of citizens. One might respond: "Well software shouldn't have those holes! Just because it's closed source, doesn't mean that won't happen anyway Also true, in an idea…

The price increase required by the higher quality of software is roughly a fixed factor. The benefits that come from code reuse are exponential.

If a government can't afford to release the sources in public right away, a gradual transition is possible: vendors that offer open source software have their prices multiplied by 0.1 during bidding. And this factor of preference for open source can be increased or decreased state-wide depending on the budget.

Re: Public Money, Public Code

#88

The state I lived in developed one of those covid tracking apps. I asked for the source code and was told it wasn't available and would never be. I talked to people working on other software developed for the state and they all think that software shouldn't be public. It seems crazy to me that taxpayers pay for this software but it doesn't belong to them. Knowing what I do know I gotta wonder if it's just about those…

This is the kind of issue that causes all that government bloat... If I was a state employee and I wrote the app, and I had to release the source code, then I'm making it very easy for a bad actor to find a vulnerability and exploit it to leak the data of citizens. One might respond: "Well software shouldn't have those holes! Just because it's closed source, doesn't mean that won't happen anyway Also true, in an idea…

> However security by obscurity is a layer of defense...

It's not: https://en.wikipedia.org/wiki/Security_through_obscurity#Cri....

See also: https://en.wikipedia.org/wiki/Kerckhoffs's_principle.

Re: Public Money, Public Code

#89
post #76

Earlier quoted context omitted.

> Hence it also increases the cost for the taxpayers Isn't that just a short-term problem? Mid to long term, it should decrease costs dramatically.

How so? Because of external contributors? Most software developed for the public sector is quite use-case specific (and the use-cases are often quite boring), so I don’t see that happening for most projects.

Once a workflow is adopted, it becomes normal and the hassles start to go away. That 3rd party library with an incompatible license now has a good alternative, code re-use is higher, handing off to new developers is easier, and identifying development teams that are highly inefficient (or incompetent) becomes possible.

I feel like there's too many benefits to even list. Having seen some of the proprietary code developed for 3 letter agencies, it's shocking how bad some of it is (and there's even projects that have better open source alternatives that solve every use-case) and adding transparency can only be a good thing... in my opinion.

Post reply on HN