3 ms·
As I said: with this setup, all the readers (everyone but me) do not even hit any Wordpress code anymore. It truly is a static site generator. You can look at t
by Tomte 5y ago
As I said: with this setup, all the readers (everyone but me) do not even hit any Wordpress code anymore. It truly is a static site generator. You can look at the generated HTML files in the file system. That's what the web server serves.
- speedgoose 5y agoIf you can login or comment, you do hit Wordpress code right? It could be fine if you put the admin portal behind a firewall but I would also recommend moving forward and stop developing new websites using Wordpress if you care about security. And you should probably care about security.
- KarlKemp 5y agoIf it generates something, it can still do whatever it wants with the generated files if the purpose is to, for example, embed spam links. If the server is the target, it either still has access to it, or to some alternative computer which, for a private individual writing a blog, will be their much more valuable personal device. Yes, you can spin up a VM, generate html, run it through all sorts of tests and only then upload it. The victims of this hack aren’t going to do that.
- Tomte 5y agoThat's a threat model that is wildly imaginative. Tell your web server to only serve the login stuff to you (certificates, HTTP Basic Auth, whatever). Problem solved. And what is your solution? A SSG also generates something and could embed bad stuff. Something has to upload your SSG generated files and thus needs access to your web server. If you're running it on your personal device it could compromise it. Really, stop trying so hard to invent Wordpress problems. If you don't like it, nobody forces you to use it.
- ifdefdebug 5y agoDid you remove all the code pages? Otherwise, an attacker is not restricted to following links on your site, they can access the code urls directly?
- Tomte 5y agoNo, they can't. As I said, the nginx or Apache configuration makes sure. Look it up, you're routing everything to static files in file system directories. Only if you are requesting an URL (however "you" are identified) the webserver even contemplates serving something else. It's an explicit rule for the special case. Everyone else doesn't see a PHP-FPM execution path at all.