jmulkerin said: > Yeah but it protects passwords much better than no compiling.
There are much better ways to use password authentication than by hardcoding passwords into your scripts/programs, however. For example, a credentials file with proper permissions. Or a private database that stores credentials. Or PAM. Or, there's always public/private key authentication instead of passwords, altogether. Obviously, I don't know the nature of your DBI script, but I doubt perlcc is the way to go about making passwords secure. Besides, UNIX 'strings' could probably pull the passwords out of a perlcc-compiled program with little effort. Colin -- Colin W. Wetherbee http://hydrogen.denterprises.org/
