JPyObjC Dude writes: When designing any system that requires automated privileged access to databases or services, developers often rely on hard coding (embedding) passwords within the source code. This is obviously a bad practice as the password is then made available to anybody who has access to the source code (eg. software source control). Putting the passwords in configuration files is another practice but it is still quite insecure as cracking hashed passwords from a text file is still a trivial exercise.
[Q] What do you do to manage your application passwords so that your system can stil run completely automated and yet make it as difficult for hackers to get their hands on this precious information?
Slashdot Top Deals
PL/I -- "the fatal disease" -- belongs more to the problem set than to the
-- Edsger W. Dijkstra, SIGPLAN Notices, Volume 17, Number 5