I gussing you manged to convert the passage back to plain text?
Nope; I didn't try... in general, this group tries to give overall
best-practice guidance; for the average programmer (i.e. writing
business code), attempting your own crypto code is a very bad idea,
and is likely to be insecure. Likewise storing passwords purely for
user-authentication purposes is usually a mistake. This was the best-
practice knowledge that I was trying to impart.
I created this using MD5 and Tripel DES
Again, in best-practice terms, AES and SHA [2 or higher] variants
would be adviseable, since both MD5 and Triple DES have weak-spots;
but if the exercise is to further your knowledge of enryption (rather
than to protect your employer's money), then fine.
You didn't specify that you intent was academic; ok - if you want to
roll encryption, and you know what you are doing - great! However, if
you want meaningful assessment of your efforts, then you'd do a lot
better on a security / encryption forum - where people have the
expertise and tools to tear your cipher to shreds (or not, depending
on how good it is ;-p). The real test is: if you post the code
(excluding any private keys), does it remain secure? [that is
rhetorical; please don't post it - just ask the question of your
code]. If not, it isn't secure.
Marc