3 ms·

You should make running WordPress securely a thoughtless process. The best practices should be clearly explained to every single user who downloads/installs it.

by dcurtis 16y ago

photomatt 16y ago
Sure -- the simplest way to keep it secure is just keep it updated. To this end we work with numerous third-party hosts to help them update their customers, and have invested significantly in a notification and upgrade system for 10k+ plugins, 1k+ themes, and of course the core software. This was a particular PITA because runs on so many platforms with wildly different constraints and configurations. We blog, tweet, and email 200k people whenever there's a new release and offer free help on our forums to anyone who is stuck. Someday we might even offer auto-update in core just like many hosts already do. My comment was more aimed at the HN audience which might want pro tips for staying updated or more defense in depth. For example I have a cron job run `svn up` on my site every morning which keeps it up to date whether I'm in front of my computer or on a beach sipping mai tais.
- chaosmachine 16y ago
  "I have a cron job run `svn up` on my site every morning" Can you really trust that not to randomly break your site? Surely you'll run into regressions or backwards-incompatibilities at some point?
  - photomatt 16y ago
    What I suggest for most folks is to tie it to a stable branch, that way you get overnight fixes but nothing potentially backward-incompatible. When a major release comes out, you need to svn switch to the new branch. Many folks in the WP community, including myself, svn up to trunk. I wouldn't recommend that for the general public, but I think it's only broken my site once in the past year and I fixed it by running svn up again. If I was smarter I would script it to svn up, check the site, revert if it was blank. WP.com syncs to WordPress trunk pretty regularly, as well, sometimes daily depending on where WP is in its release cycle or if we have to do any database migrations.
thenbrent 16y ago
You're trying to say WordPress is to blame for not making server administration, across multiple * nix flavours thougthless. WordPress has secure defaults and the codex does a good job of providing instructions if you really want to go modifying the default. There will always be tutorials out there saying chmod 777 * Rookie users will follow these tutorials and then blame WP because they find a whole bunch of malicious scripts show up in their wordpress directory. EDIT: formatting

You should make running WordPress securely a thoughtless process. The best practices should be clearly explained to every single user who downloads/installs it.

by dcurtis 16y ago

You should make running WordPress securely a thoughtless process. The best practices should be clearly explained to every single user who downloads/installs it.

photomatt 16y ago

Sure -- the simplest way to keep it secure is just keep it updated. To this end we work with numerous third-party hosts to help them update their customers, and have invested significantly in a notification and upgrade system for 10k+ plugins, 1k+ themes, and of course the core software. This was a particular PITA because runs on so many platforms with wildly different constraints and configurations. We blog, tweet, and email 200k people whenever there's a new release and offer free help on our forums to anyone who is stuck. Someday we might even offer auto-update in core just like many hosts already do. My comment was more aimed at the HN audience which might want pro tips for staying updated or more defense in depth. For example I have a cron job run `svn up` on my site every morning which keeps it up to date whether I'm in front of my computer or on a beach sipping mai tais.

chaosmachine 16y ago
"I have a cron job run `svn up` on my site every morning" Can you really trust that not to randomly break your site? Surely you'll run into regressions or backwards-incompatibilities at some point?
- photomatt 16y ago
  What I suggest for most folks is to tie it to a stable branch, that way you get overnight fixes but nothing potentially backward-incompatible. When a major release comes out, you need to svn switch to the new branch. Many folks in the WP community, including myself, svn up to trunk. I wouldn't recommend that for the general public, but I think it's only broken my site once in the past year and I fixed it by running svn up again. If I was smarter I would script it to svn up, check the site, revert if it was blank. WP.com syncs to WordPress trunk pretty regularly, as well, sometimes daily depending on where WP is in its release cycle or if we have to do any database migrations.

thenbrent 16y ago

You're trying to say WordPress is to blame for not making server administration, across multiple * nix flavours thougthless. WordPress has secure defaults and the codex does a good job of providing instructions if you really want to go modifying the default. There will always be tutorials out there saying chmod 777 * Rookie users will follow these tutorials and then blame WP because they find a whole bunch of malicious scripts show up in their wordpress directory. EDIT: formatting