Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For instance. If I want to write to a SQLite db file, then I need to make the directory writable.
On the other hand, they say that you should not put the database in the webroot directory.
But even if I put the database in any other directory, I still need to give write access to that directory to allow apps to read and write to the database. Isn't that a kind of "chicken and egg" problem?
It's confusing the hell out of me.
IS there *ANY* way to write a secure SQLite application or simply forget the idea and go with MySQL or other?
You shouldn't need to make the directory writable, it should just need to be the file. SQLite uses filesystem permissions for security which should be at least as strong if not stronger than other authentication. You are correct about keeping it out of your webspace though, unless you want people to download it ofcourse.
SQLite uses filesystem permissions for security which should be at least as strong if not stronger than other authentication. You are correct about keeping it out of your webspace though, unless you want people to download it ofcourse.
I tried making the file writable and the directory non-writable. It doesn't work. I get a error whenever I try to update the database.
Of course, I have found a way out: Keep the db in a separate folder, use .htaccess to deny permissions to that folder and it works now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.