With the current setup, if I include a .htaccess for the DB dir, this will only work for Apache - not IIS.
I know I can include a warning about how important it is to place the files outside the HTTP directory tree and .htaccess files are good, but it is just too easy to download an SQLite DB... I can't really see any PHP use that would be OK for this really.
if I put the db file "SQLITE.DB" into /www/db
Anybody can d/l it by typing
http://myserver.com/db/SQLITE.DB
I though I might even be able to prevent d/l by naming the DB file with a "." at the start but it makes do difference.
... and if the project is open source it is just too much of a security risk as everybody knows where the file is going to be on a default installation.
Otherwise I'm stuck with the standard PHP prefs file "confing.inc.php" (- which is safe from prying eyes):
<?
if (defined("correct_entry_point")) {
my_pref[1] = "lots of good stuff";
}
?>
But updating this on pref changes is no fun compared to SQLite....
<shrug>
Please somebody tell me I'm wrong, Cheers, Adam
-- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
