• Danterious@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    27
    arrow-down
    1
    ·
    7 months ago

    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
      link
      fedilink
      arrow-up
      14
      ·
      7 months ago

      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
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        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
          link
          fedilink
          arrow-up
          3
          ·
          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”.