> And why does no other CMS system or framework come even close to the number of critical vulnerabilities in Wordpress?
Because no other CMS or framework has as many deployments. Not even close.
> If "flexibility and complexity equal vulnerability" then why does the linux kernel, 53x the size of Wordpress and a tad more complex than a CMS, not have about 53x more exploits?
Because it's behind a firewall. Do I really need to keep repeating myself?
If I could send remote commands to your kernel, don't you think there would be a few more exploits kicking around?
> Huh? SSH, Postfix and nginx are usually not firewalled.
If you're not restricting access to SSH using a firewall, then you're a bigger idiot than I thought you were.
>If you're not restricting access to SSH using a firewall, then you're a bigger idiot than I thought you were.
I'm not sure name calling is really appropriate here. Yes, firewalling stuff is certainly appropriate, particularly administrative things, but key based auth is pretty secure, firewall or no.
You're also nitpicking on a single point when he mentions other things that are definitely not usually firewalled. Your mail and web servers are generally open to the world, regardless of whether or not SSH is.
Because no other CMS or framework has as many deployments. Not even close.
> If "flexibility and complexity equal vulnerability" then why does the linux kernel, 53x the size of Wordpress and a tad more complex than a CMS, not have about 53x more exploits?
Because it's behind a firewall. Do I really need to keep repeating myself?
If I could send remote commands to your kernel, don't you think there would be a few more exploits kicking around?
> Huh? SSH, Postfix and nginx are usually not firewalled.
If you're not restricting access to SSH using a firewall, then you're a bigger idiot than I thought you were.