Technology

60042 readers

4874 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

533

Switzerland mandates government agencies use open-source software and disclose the source code of software developed by or for the public sector unless third-party rights or security concerns apply (www.tomshardware.com)

submitted 4 months ago by ForgottenFlux to c/technology

22 comments fedilink hide all child comments

Switzerland has recently enacted a law requiring its government to use open-source software (OSS) and disclose the source code of any software developed by or for the public sector. According to ZDNet, this “public body, public code” approach makes government operations more transparent while increasing security and efficiency. Such a move would likely fail in the U.S. but is becoming increasingly common throughout Europe.

According to Switzerland’s new “Federal Law on the Use of Electronic Means for the Fulfillment of Government Tasks” (EMBAG), government agencies must use open-source software throughout the public sector.

The new law allows the codifies allowing Switzerland to release its software under OSS licenses. Not just that; it requires the source code be released that way “unless the rights of third parties or security-related reasons would exclude or restrict this.”

In addition to mandating the OSS code, EMBAG also requires Swiss government agencies to release non-personal and non-security-sensitive government data to the public. Calling this Open Government Data, this aspect of the new law contributes to a dual “open by default” approach that should allow for easier reuse of software and data while also making governance more transparent.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 25 points 4 months ago (4 children)

I mean wouldn't everything be a security concern in relation to government agencies?

[–] [email protected] 34 points 4 months ago

I work for the UK government. Everything my organisation does is licensed in either MIT or OGL (https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/)

Developing code in the open really helps ensure you nail down your secure coding practices.

[–] [email protected] 14 points 4 months ago (1 children)

In my opinion especially security code needs to be open source…

[–] [email protected] 5 points 4 months ago

Nothing like bored programmers on the internet to nitpick the governments code.

[–] [email protected] 11 points 4 months ago (2 children)

If you don't release your source code due to security concerns, you just announced to the world that your software is vulnerable and you're relying on security through obscurity.

[–] [email protected] 3 points 4 months ago

never let them see you cry

[–] cybersandwich 3 points 4 months ago

Meh, not really. The risk with making it publicly available is that a nation state or leet hacker types can comb over it and find exploits or know what libraries/etc you are using so when a zero day pops up they can target you directly. Whereas without direct access to th source code they'd have to do their own enumeration and surveillance.

There is some security through obscurity.

Also, just want to point out: being open source doesn't mean it's more or less secure. There is plenty of vulnerable open source code out their.

[–] [email protected] 7 points 4 months ago

I feel like a lot of the front ends can be open sourced.