| 6:44 pm on Sep 19, 2008 (gmt 0)|
| 7:04 pm on Sep 19, 2008 (gmt 0)|
I know I could validate the values off a server database and that would protect visitors from finding out the valid entries, but are there any other options? Thanks.
| 7:08 pm on Sep 19, 2008 (gmt 0)|
Even if you do make it look up the values off a server, a coder could very, very easily make your script do an alert to display the values after lookup.
| 8:07 pm on Sep 19, 2008 (gmt 0)|
| 1:44 pm on Sep 21, 2008 (gmt 0)|
|Can you point me to an explanation of how to do this? |
Not exactly. There is no pre-made script to do what you want. But if you explain precisely what you want to do in the PHP or Perl forums I'm sure those guys will have something to hand.
| 8:54 pm on Sep 21, 2008 (gmt 0)|
| 7:11 pm on Sep 22, 2008 (gmt 0)|
Oh, ok you're using sendmail? Is this one of those 'enter these characters' things to protect against spam?
If you already have a Perl sendmail script, it would be much safer to put any validation in there. It's secure, users can't mess, so much more reliable.
| 8:49 pm on Sep 22, 2008 (gmt 0)|
I'm using a Perl sendmail script already, so I'll plan to add the edit right there. The field I'm editing isn't a spam protection field. Thanks for helping me sort thru this. I appreciate it!
| 9:45 pm on Sep 25, 2008 (gmt 0)|
This will avoid the need of server side scripting, although that's the right solution.
[edited by: engine at 10:35 am (utc) on Sep. 26, 2008]
[edit reason] no sigs/urls, thanks [/edit]
| 5:17 pm on Sep 26, 2008 (gmt 0)|
An obfuscator will not solve the problem, as the code can easily be reformatted/beautified into a readable format. And values (like the strings you're matching against) would not be changed. A server side solution is the only reliable solution.