This really depends on how you're deciding who gets to see
what. I assume
this means that you've got a logged-in user with an active
session. In that
case, the best thing you can do is to not assume that a
record may be
retrieved just because it's requested. Whatever you do to
filter the list
of available choices, perform the SAME check when retrieving
the record. If
the check fails, shoot a little e-mail to yourself along with
the logged-in
user's account ID so you know who's trying to do a little
unauthorized
snooping.
"hconnorjr" <webforumsuser@macromedia.com> wrote in
message
news:euc7i5$hv4$1@forums.macromedia.com...
> To protect my database from hacking I'd like to encrypt
the ID information
> displayed in my URL. for example, currently the URL
displays
>
>
http://www.abc.com/results_details.php?result_ID=2
>
> or something similiar depending on the ID number of the
record. But
> wouldn't
> it be more secure to take each of those ID numbers and
run them through an
> encrption scheme (md5, salt) and store them with the
record? Then, when I
> pull
> the records for a recordlist I can pull the encrypted
identifier. The MORE
> INFO
> link will go the same record as before, but the URL will
show . . . .
> .php?359tifna[0sfh[w0frhas0fj (or whatever the hash has
generated)
>
> can anyone give me tips on the easiest way to do this?
>
> thanks in advance for all help.
>
> mike
>