Zum Inhalt der Seite gehen


Keep in mind that just because an application is open source doesn't mean it's safer. If nobody checks its code for bugs or malware, it could be worse than other software.

----

We have so many questions that are making us feel a bit uneasy: ❓

In what ways can you be certain that a particular open-source software solution is secure?

What factors do individuals with an IT background consider when making decisions about open source software safety?

Certain open source software solutions have extensive code bases. Consequently, it would require a significant investment of time to verify the absence of bugs or malicious code. 🐞 ☠️

That said, even those who can understand code may not always have the time or energy to investigate every piece of software they install. So what are their criteria for endorsing a particular piece of software that they haven't analysed its code? 🧭

And what tips do you have for people who aren't developers, to help them make the best choices when they can't understand the code? Who can they trust?

#opensource #cybersecurity
I think crucial parts is looking at it's components, dependencies, size and for apps permissions.#ReproduceableBuilds for example are important, so the actually released source code is what people actually get served as basis.Plus in terms of #security, choose *real #E2EE with #SelfCustody of all the #Keys!
That's true, open source doesn't always mean the best solution.

Checking reproduceable builds looks a little bit complicated but it would be great if we could do it easily! 🤔
@monocles It's true that #Conversations and its fork #MonoclesChat are reproducible today, yet they are not setup like this historically (signed by F-Droid). While we push for reproducible builds, these are not a must, but an extra check of trust.

https://f-droid.org/docs/Inclusion_How-To/#reproducible-builds