this post was submitted on 09 Apr 2024
160 points (99.4% liked)

Open Source

31243 readers
295 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

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
[–] Danterious@lemmy.dbzer0.com 28 points 7 months ago (7 children)

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.

[–] taladar@sh.itjust.works 16 points 7 months ago (5 children)

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.

[–] Name-Not-Applicable@kbin.social 2 points 7 months ago (1 children)

Just because someone else wrote it, doesn't mean it's a good implementation, or worth bringing its pile or dependencies into your project.

[–] taladar@sh.itjust.works 3 points 7 months ago

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".

load more comments (3 replies)
load more comments (4 replies)