• Valarie@lemmygrad.ml
    link
    fedilink
    arrow-up
    1
    ·
    2 days ago

    I dont think cars should connect to the Internet if you don’t want them to so live commands shouldn’t be an issue but if you are talking about programming preset commands in having the apps be open source would fix that for the most part by adding that auditing layer

    • Ferk@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      2 days ago

      Open source software is not bug free. I’d argue there are more vulnerabilities caused by human error than there are caused by malicious actors. More often than not, malicious actors are just exploiting the errors/gaps left by completely legit designers.

      Running those open source apps in a separate computer, isolating infotainment from the more critical software, would be an even stronger safety layer, imho.

      • Valarie@lemmygrad.ml
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        They aren’t bug free but that is the same as closed source and requiring open source would prevent malicious actors from doing as much while also letting anyone who wanted to pentest and granularly access the code have complete access and find as many if not more weaknesses than a dedicated corporate bug hunting team

        • Ferk@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          2 days ago

          I agree, which is why I think running those open source apps in a separate computer, isolating infotainment from the more critical software, would be a stronger safety layer.

          Them being separated should, imho, be a precondition, so that it can minimize accidents and exploits in cars that might be running software that is not immediately up to date as a result from publicly and well known vulnerabilities being discovered as the code evolves.