3 ms·

Why does a plugin system immediately imply sandboxing?

• eviks 5mo ago
  Because a box is an intuitive way to limit the blast radius of arbitrary code? But the wasn't a requirement, I'd be fine with sandbox-free secure plugin systems
  • pdntspa 5mo ago
    There are tons and tons of successful plugin systems out there that do not have such ridiculous requirements. I have thousands of VSTs installed and have never been RAT'ed. What happened to practicing internet hygiene? At some point we need to acknowledge the problem is cultural, and address accordingly. I realize that the business objective for many is to make computing as brainless as possible but we need to be pushing back on that. Instead we have forums full of really smart people demanding a nanny state. Yuck -- what a sad and pathetic state of affairs.
    • eviks 5mo ago
      > What happened to practicing internet hygiene? Nothing happened, it never worked, and the more people got exposed to the internet, the more obvious it was, your personal RAT history notwithstanding. Post your own hygiene list in some security-related public forum and get some comments on how easy it is to circumvent it and/or how impossible it would be to comply with > tons of successful plugin systems The requirement here is secure, not generically successful. Tons of bad insecure systems get popular > problem is cultural, and address accordingly That's exactly what all those sandbox and permissions do - address the cultural problem of the impossibility of following a set of very stringent rules without a fault at an individual level when there are more than a few individuals