3 ms·

To be fair, WordPress core has gotten better. The bigger problem is that there are many WordPress plugins, and many of the plugins can't even pretend to be rela

To be fair, WordPress core has gotten better. The bigger problem is that there are many WordPress plugins, and many of the plugins can't even pretend to be related to being secure. Until developers are widely taught how to develop secure software, the problem will just keep moving around. We can't make software development environments where it's impossible to create a vulnerability, and we will never convince users to stop wanting new capabilities. Making things secure in the first place needs to be part of the solution.

berkes 3y ago
Very over the top, but bear with me. For example: if your community of plugin developers cannot produce secure(ish) plugins, then it's probably time to get rid of the plugin system altogether. "Plugins endanger our users, we no longer allow them." Being a player that powers a vast part of all websites, gives a responsibility. Taking up that responsibility includes making unpopular decisions. While "getting rid of the entire plugin system" is probably a bridge too far (it would kill WP instantly) the system needs overhaul (same for hosting, same for themes), badly. There is an intermediate solution, I am sure¹. But the starting point must be "our community cannot handle the power we give it, so let's find a solution for that". ¹ I refrain from concrete examples here, bc HN tends to spiral into discussions on why random potential solution X will never work. I want to keep this on a higher level.
- quickthrower2 3y ago
  Do what Chrome has done and continually improve plugin security. Plugins should ask for permissions. Would require an overhaul of WP though.
  - berkes 3y ago
    That, and/or a sandbox model where plugins cannot escape a sandbox. And/Or a setup where a plugin's runtime is isolated from main WP and other plugins and it can only communicate with WP over a tiny and very much hardened API. so many possibilities. This problem has been solved mostly. Just not for PHP (that I know) and certainly not for WP.

berkes 3y ago

Very over the top, but bear with me. For example: if your community of plugin developers cannot produce secure(ish) plugins, then it's probably time to get rid of the plugin system altogether. "Plugins endanger our users, we no longer allow them." Being a player that powers a vast part of all websites, gives a responsibility. Taking up that responsibility includes making unpopular decisions. While "getting rid of the entire plugin system" is probably a bridge too far (it would kill WP instantly) the system needs overhaul (same for hosting, same for themes), badly. There is an intermediate solution, I am sure¹. But the starting point must be "our community cannot handle the power we give it, so let's find a solution for that". ¹ I refrain from concrete examples here, bc HN tends to spiral into discussions on why random potential solution X will never work. I want to keep this on a higher level.

quickthrower2 3y ago
Do what Chrome has done and continually improve plugin security. Plugins should ask for permissions. Would require an overhaul of WP though.
- berkes 3y ago
  That, and/or a sandbox model where plugins cannot escape a sandbox. And/Or a setup where a plugin's runtime is isolated from main WP and other plugins and it can only communicate with WP over a tiny and very much hardened API. so many possibilities. This problem has been solved mostly. Just not for PHP (that I know) and certainly not for WP.