• :arch: bitterseeds
    link
    fedilink
    36 months ago

    @possiblylinux127 @wisha And how would sandboxing a malicious script inside a theme that is supposed to change the look of your desktop work? They installed and ran something that rm’d their home directory. I’m honestly curious how you’d solve this.

    • @[email protected]OP
      link
      fedilink
      96 months ago

      A more locked-down theming API could help. For example Firefox themes are always 100% safe to install. That said, Firefox themes are almost useless (they’re more like color schemes lol), and no one wants to lose KDE’s powerful customizability so 🤷🤷

      • @[email protected]
        link
        fedilink
        46 months ago

        Perhaps having different categories with different limitations would work well. Using the firefox example, prioritize the use of WebExtensions, but keep XUL/XPCOM with appropriate warnings.

      • JackGreenEarth
        link
        fedilink
        English
        46 months ago

        What do you mean? I have Firefox themes that change the whole look of the browser, using userchrome.css.

        • Kayn
          link
          fedilink
          2
          edit-2
          6 months ago

          That’s obviously not what OP was referring to when mentioning “Firefox themes”.

          • JackGreenEarth
            link
            fedilink
            English
            16 months ago

            Maybe, I was showing that there were better ways to theme Firefox though

    • Possibly linux
      link
      fedilink
      English
      36 months ago

      If it ran in a sandbox it would just wipe its own files instead of the system. Under no circumstances should a plugin from some random guy online be running with such high privileges

    • @[email protected]
      link
      fedilink
      16 months ago

      SELinux? Apparmor? (Serious question, I don’t know if there might be features that render those two inadequate)