Justin, Sorry, I guess I didn't communicate my question well. Accidently forgot to bring the extra cup of coffee with me...
I'd like a page that would let a limited number of people edit data. That's what needs protection, the page that writes and edits data. Everyone can see the data, though putting it outside the webroot is a good idea in it's own right. So in the document root we'd have a page "edit_database.php". That's what needs protecting, I think. Make more sense? Thanks! Leam -----Original Message----- From: talk-boun...@lists.nyphp.org [mailto:talk-boun...@lists.nyphp.org] On Behalf Of Justin Dearing Sent: Monday, May 03, 2010 7:40 To: NYPHP Talk Subject: Re: [nyphp-talk] Password security for SQLite based pages? Why not just store the SQLite file somewhere outside of the webroot? Justin On Mon, May 3, 2010 at 7:38 AM, Hall CTR Leam <leam.hall....@usmc.mil> wrote: Morning all! I'm looking to not use MySQL for some web pages, but to instead try SQLite. There's nothing in the database that would need to be protected from reading, and it's a small site that doesn't need a full blown database. However, I'd like to limit access to updating. Would it be enough just to have a web page that you had to log in via .htaccess? Is there a better way? Thanks! Leam -------------------------------------------- Leam Hall UNIX Systems Administrator Contractor for Smartronix ( CMMI Level 3 ISO 9001:2000 FS 91000 ) Com: 229.639.6028 Email: leam.hall....@usmc.mil -------------------------------------------- _______________________________________________ New York PHP Users Group Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk http://www.nyphp.org/Show-Participation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ New York PHP Users Group Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk http://www.nyphp.org/Show-Participation
