Hakan VELIOGLU said: > Hi, > > I have a server that users are accessing it with ssh and publishing their > web > sites. What I want is a database support with less effor. So, > SQLite is a very good option for me to decrease the management tasks for a > database support. However, I searched the SQLites's web site for security > tasks but I couldn't find any sugestion. > > What I need is some suggestions like don't give the 777 permission to a > database > file. :) Of course this is very simple, but I am a newbee in SQLite so I > need > your experiments.
What are you trying to accomplish with your database, and your database security? That said, unless you buy the encrypting version of the database your only real options for securing a database file are through filesystem permissions. Set the filesystem permissions appropriately and things should be okay. If the database needs to be accessible from a web app the best solution is to create the database outside of the web server's document root in a folder that only the web server and the site owner have permissions to read, write or execute. That's folder permissions 770 with the owner or the group being the web server's owner or group, and the group or the owner being the user. >From there keeping miscreants out of the file becomes the domain of the web application accessing that file. The app writer can give as much or as little access as desired. Clay Dowling -- Simple Content Management http://www.ceamus.com
