• Pika@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    16 days ago

    man, arcane looks amazing, I ended up deciding off it though as their pull requests look like they use copilot for a lot of code for new features. Not that I personally have an issue with this but, I’ve seen enough issues where copilot or various AI agents add security vulnerabilities by mistake and they aren’t caught, so I would rather stray away from those types of projects at least until that issue becomes less common/frequent.

    For something as detrimental as a management console to a program that runs as root on most systems, and would provide access to potentially high secure locations, I would not want such a program having security vulnerabilities.

    • MangoPenguin@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      3
      ·
      15 days ago

      I wouldn’t be exposing any management consoles to the internet either way, too much risk with something that has docker socket access.

      • Pika@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        15 days ago

        fully agree, mine isnt accessible to the outside world either but, you never know if something gets missed or somehow a path gets made. would rather not open up that risk

    • dan@upvote.au
      link
      fedilink
      English
      arrow-up
      3
      ·
      16 days ago

      a program that runs as root

      Does it have to run as root? It’s common to run Docker in rootless mode in production environments.

      • Pika@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        16 days ago

        while docker does have a non-root installer, the default installer for docker is docker as root, containers as non-root, but since in order to manage docker as a whole it would need access to the socket, if docker has root the container by extension has root.

        Even so, if docker was installed in a root-less environment then a compromised manager container would still compromise everything on that docker system, as a core requirement for these types of containers are access to the docker socket which still isn’t great but is still better than full root access.

        To answer the question: No it doesn’t require it to function, but the default configuration is root, and even in rootless environment a compromise of the management container that is meant to control other containers will result in full compromise of the docker environment.

    • nublug@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      8 hours ago

      ugh well that sucks butt. i’ll be trying new alternatives tonight i guess lol

      any recommendations?

      update for posterity: i ditched arcane for just managing compose files manually and lazydocker for logs and restarting containers. it’s plenty good for my needs at the moment. tried komodo and couldn’t get it working and didn’t quite like any others i looked into so i dunno what to recommend for a webgui docker manager.