I always thought that web hosting companies would be decent enough to provide security but they do not.
They cannot protect you from people modifying dynamic content such as your blog. Here's how it works.
When you upload your blog your hosting company, it will have a username and password for the database to which it should be connected to.
Each file has the following permisssions: your_username:your_username . The first item before the colon means that's the username, and the second indicates the group. Yeah, you are a member of your own group. Stupid eh?
When you upload a file to your host, the default permissions are:
You can read and write into the folder/file
Your group can read and write into the folder
Everyone can read
Yeah, everyone can read. The reason behind this is that the webserver process, which runs under a different username, needs to read your files. What needs to happen is that a special group between you and the web server username needs to be created. Or the username of the webserver needs to be added onto your own username. That way, you can remove read access to everyone and give read access only to yourself.
This really sucks. If you are a savy user you can find several places where you can find usernames of people in the system. Sometimes, hosting companies place everyone's username in a file for their benefit. Guess what if you thought that gave you security, tough luck.
Now you're thinking, why on earth don't they do this. The answer is stupid: they are lazy. They don't want the overhead of troubles which comes with this configuration. Making sure a user is a member may require more time on their side. So, they say: Since you can't afford to buy a VPS, you can't afford to protect your data. Yep, they think like that.. Yet another wtf for the day!
MeasureIt