Requires Free Membership to View
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.
With that said, however, best practices for encryption depend on what language you're writing in. There are two sites that come to mind (granted, googling "encrypt password" will show a number of sites with sample code): One is Encrypt HTML, which has a number of tools, not just html; the other is JavaScript Kit, which allows you to put in a password and it will generate java code for you. Good luck, and happy writing.
For more information:
- Read more about how encryption interacts with password management.
- Check out this tip on securing emerging endpoints with encryption.
This was first published in March 2010
Security Management Strategies for the CIO
Join the conversationComment
Share
Comments
Results
Contribute to the conversation