is that really secure? I just thought if for any reason, someone can get into my database, they can't just add usernames and file ids to my table and have access.
I thought if I md5 it, then it'll be more secured. would 1 table for username-fileid really be fine? thanks, Sia Quoting Stut <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] wrote: > <snipped a confusing idea> > > Any idea if this is a good way to do this or not? any better suggestions? > is > > this secured? > > I'm confused. What's wrong with having a table containing a row per > file, then having another table containing the users. Add a third table > containing two fields, username and fileid, which contains one row per > user per file they've purchased. When they try to download a file you > check against that table. > > Maybe I'm missing the point of all the md5 crap. If so, please enlighten me. > > -Stut > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
