Pfft... screw that, just encrypte the stored data (passwords for example). If someone does hack it, they won't know what encrypted it, so it would be impossible to reverse.
Pfft... screw that, just encrypte the stored data (passwords for example). If someone does hack it, they won't know what encrypted it, so it would be impossible to reverse.
- Mike
I thought of this, but was hoping someone would know of an easier way. When the code is deployed on a couple different servers, it gets annoying to have to change the SQLite file path.
The passwords are already encrypted with md5, are you talking about encrypting everything. I can imagine that would cause a performance hit.
Not really. It wouldn't take them long to realize it is a PHP script, and that there aren't that many reversible encryption schemes out there for PHP, and I don't have the knowledge to write my own.
Since I stick to Apache servers could .htaccess be used? I'm not sure how.
You could also put it in a directory under the web root without read or execute privileges, and take those privileges from the file itself too.I thought of this, but was hoping someone would know of an easier way. When the code is deployed on a couple different servers, it gets annoying to have to change the SQLite file path.I was, and it would.The passwords are already encrypted with md5, are you talking about encrypting everything. I can imagine that would cause a performance hit.There are plenty.there aren't that many reversible encryption schemes out there for PHPYes, you could:Since I stick to Apache servers could .htaccess be used? I'm not sure how.... or similar.Code:<Files mydatabase.db> Deny From All </Files>
Twey | I understand English | 日本語が分かります | mi jimpe fi le jbobau | mi esperanton komprenas | je comprends français | entiendo español | tôi ít hiểu tiếng Việt | ich verstehe ein bisschen Deutsch | beware XHTML | common coding mistakes | tutorials | various stuff | argh PHP!
Bookmarks