• Today my blog was hacked by some (rather primitive) Turkish guerrillas. I don’t know what they did and how the hell did they squeeze in, but domain name was redirected to their site.

    The server support team responded and restored the backup.
    What’s bad, I lost my last post. Of course, Murphy didn’t sleep – it was the longest text I have written.

Viewing 2 replies - 16 through 17 (of 17 total)
  • Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    He asked two questions and I gave two responses. You’re mixing them up.

    Thanks for clearing this a bit, but if I set my .htaccess to 644, what about WP updating the permalinks when I save a new post?

    If you change the permalinks structure from the admin interface in wordpress, and want wordpress to automatically change the .htaccess for you, apache needs write permissions on the file (which needs the 3rd digit to be a 6, so really 646 is fine for that). However, that’s only for changing the permalinks structure.

    The online WP manual says that it needs a 666 access in order to use permalinks. I assume this is not safe?!

    Once it is the way you want it, 644 is fine for .htaccess, which means that only you can change .htaccess.

    Suncokret understood this. Having said that, you can admit that you misinterpreted my post, or continue to feel that I insinuated the wrong message. Either way just drop it, as the original goal of this post has been accomplished.

    666 is not safe…it’s the number of the beast!

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘My WP 2.3.3 was hacked’ is closed to new replies.