Interesting question: First, I'd have to ask why you're implementing a password encryption program to begin with, instead of letting an operating system or application manage this bit of information. I assume you're asking in the context of writing the application that will manage the encryption code itself.
The general contemporary thinking in this regard is not to put passwords in code, but to use certificates, like Kerberos, or trust relationship information, like Federation SAML assertions, in the code since any hacker with enough time and energy can eventually crack an encrypted password.
For more information:
Dig deeper on Password Management and Policy
Related Q&A from Randall Gamby, Contributor
Is your remote desktop access software really secure? Randall Gamby offers advice for conducting a remote access audit to validate security.continue reading
Expert Randall Gamby discusses risk-based authentication, and whether that type of user identification system is right for the enterprise.continue reading
Expert Randall Gamby discusses various types of single sign-on, specifically the approaches of Ping Identity's SSO and Symplified SSO.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.