I'm planning a little console program to record passwords, hash them, and store them in the file. Thinking about first hashing the "master" password using SHA, then hashing again using MD5, and storing this master password in the file header. This would be for password confirmation, and the actual data would encrypted using 3DES by the previously-hashed password once it is confirmed. I've never done this level of API crypting before, and am wondering if this will suit my needs. If you're wondering why so specific, it is from a little program called Cryptex which I found.

Sorry, computer screwed up and rest was lost. Here's the rest of the model

Plaintext -> SHA hash (160 bits) -> MD5 hash (128 bits) -> File Header

Then, the plaintext data file (or input from console) would be crypted with 3DES and stored into an offset in the file. Is this the best method for what I'm going to be using? The specifics:

Takes <= 128 byte password from console or file
Takes <=128 byte username from console or file
Takes <= 128 byte "Reason" from console or file

EX: Password: 12345
Username: FoodIsGood
Message: Amazon.com

This method has proved perfect when crypting arbitrary amounts of data, but I have never done this level before...

PS: I don't really need to encrypt the passwords and such, but this program is for my mother who is has many passwords/usernames scattered around and would like it safe and sound.

Do not use MD5, it is already broken.

For SHA, i suggest using libtomcrypt.

PS: it is good customary NOT to post several times in row. Think twice, and post once.

do use md5 with a salt & pepper system, no one cares that much about your mother's passwords as to create specific rainbow tables just for them.

lol