My site is back to normal, has been since first 3-4 posts here and without anyone's help.
- File permissions are 644, directories 755.
- Originally it was 4.1 hacked in 2010. That was before warning "remove install directory" was issued, even specialist installation by VB staff left it onsite. Site re-provisioned.
- Months of experimenting with the site, Mods, plugins, messing...wiped the site and got another specialist installation (May 2011, Jake Bunce did it).
- over years, 6 times found (using Maintenance - Diagnostics) .php files that are not part of VB, a glance through and they seemed to be spam mailers.
- 2 times webhostinghub.com located and quarantined spam mailers (since they upgraded their software 3 months ago)
- 1 time found (last week) a file "class.php" in the includes directory
- on Monday the site was hacked and taken down
Keep on changing passwords into 40 characters long, spaces, mixed letters.
Daily run of Diagnostics. Daily backups.
--------------- Added [DATE]1441871454[/DATE] at [TIME]1441871454[/TIME] ---------------
Quote:
Originally Posted by cellarius
This debate is ridicoulous. Every webscript I have ever used has database credentials in plain text in a config file. There's just no other way to do it, since the script has to be able to access this information. Of course you could encrypt it, but since the script needs to be able to decrypt it again to use it, you'd have to store the key somewhere. As others have pointed out, the config file can't be accessed from the outside. If an attacker has access to your ftp or shell, it's really too late.
Let's see why this debate is ridiculous: because coders and VB staff participating here have not told us (may well be news to them) that plain text database admin user name and password in
/includes/config.php
are used when initially creating the database from the sheet supplied for paid install or from own notes. Some may stay with that password, most would change it.
Just changed my cPanel, mail and database passwords and in
/includes/config.php
the password is the same as it was upon creation, should not be valid. But the site does not care.
That is another question: why is it then in /includes, why not in /install and removed before the site is powered up?
09-10-2015, 05:42 AM
Threaded Mode