3 ms·
Many of them could remain mostly as-is in the case where the database is local, as they already ask for the database name and password, and don't move forward u
by tyingq 9y ago
Many of them could remain mostly as-is in the case where the database is local, as they already ask for the database name and password, and don't move forward until it's right.
So just adding the extra step when a remote database is specified might suffice, and preserve the easy install for most users.
- nsgi 9y agoAs discussed in the article, this is still potentially insecure when using shared hosting.
- TazeTSchnitzel 9y agoThat won't help you if your username is "root", your password is "", your hostname is "localhost" and your database is "database".
- hannob 9y agoThat was my initial idea I proposed as a fix. However I am not really comfortable with it and came to the conclusion I don't think it's a good fix. Ultimately that makes a pretty bold assumption: That if you have database credentials on a host this allows you to control other people's webapps in some situations. That's not reasonable. I could just be another customer at a webhoster and I don't think it's reasonable to assume that customers are allowed to hack each other. I think a real additional authentication step for all installations is the right solution.
- tyingq 9y agoSure. Shared hosting usually uses remote databases, though I suppose you could install a DB locally and fire it up. That assumes you land on the same physical host as your victim, which isn't likely at all but the smallest hosts. And, shared hosting is pretty risky anyway :). But I do get your reasoning.