← Back to context

Comment by troad

2 days ago

No permissions system, nothing resolved. Plugins still have access to everything - full disk, network, etc. How does one even speak of security vulnerabilities when the security model of Obsidian plugins is just straight up "click here for RCE".

All I see is a spanking new interface that will accelerate the pace of plugin turnover, bringing forward the next inevitable security incident.

14 comments

troad

Reply
kepano  2 days ago

It seems like you have not read the blog post.

  • rtrgrd  2 days ago

    Just wanted to say a huge thankyou for being so patient in the forum; it's quite annoying that the comment section is a more a function of the title + personal opinions than a function of the blog content.

    I love using obsidian, and thanks so much for all the work that you and the team have put in :)

  • troad  2 days ago

    I have indeed read the blog post. Can you point out which part of my post is inaccurate? It is certainly possible I misunderstood something.

    Surely you're not about to claim that asking plugins to "disclose" what resources they use is in any way comparable to sandboxing and permissions.

    • kepano  2 days ago

      As I wrote, yes, a permission system is planned. But 1. we cannot oversimplify the problem of getting from here to there, 2. permissions are not a panacea. If you look at the scorecards for a few plugins you'll immediately see issues that a permission system wouldn't catch.

      Millions of people depend on thousands of Obsidian plugins. We cannot just flip a switch and break everyone's workflows overnight. It will be a gradual process. We're working on it, and I hope you'll at least concede that this is better than nothing.

      7 replies →