164
this post was submitted on 09 Apr 2024
164 points (99.4% liked)
Open Source
31122 readers
293 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Semi related to this I think a good way to avoid back doors in open source software is to have as few dependencies as possible. So I appreciate that this is a thing.
Maybe it avoids backdoors but it also avoids the maturity and security of using shared implementations for common tasks in favour of half-assed implementations in your own code.
Just because someone else wrote it, doesn't mean it's a good implementation, or worth bringing its pile or dependencies into your project.
True, but the opposite is true too, just because you or one of your team members wrote it that doesn't mean it is a good implementation. Especially considering your team can not have domain experts on everything. There is reason the rule is "never roll your own crypto" and not "crypto is security relevant, always roll your own".