Gullanian wrote:
I would use md5, but I figure id get more marks if I wrote my own encryption method. |
Sorry to be a spoil sport here, but you are never better off designing your own encryption scheme. Home baked security is ok for putting off casual 'hackers' but won't stop someone who is more determined, and those are the people you should be worried about. I know guys that have some serious resources and skills for cracking into systems. Those are the people I design my security for. [ I'm not too bad myself, but they are better than me. ]
MD5 is very good, especially if you use it properly with a salt string. Combined with SSL and SafeKey (http://www.syworks.com/safekey/index_eng.html) you have a damn near impregnable combination.
Commercial encryption components are often better than MD5, but since MD5 is open, and has withstood a good amount of scrutiny, it can be trusted. Commercial solutions sometimes have holes.
I don't really like MD5 because it's a hash, and I like to know what's going on
.
Password crackers are abundant. John the Ripper, ALZip (for zip files), etc. But they won't help you. You'll have to build your own.
This is my 4 step program to hacking a system:
1) Network sniffing - steal the info close to the source
2) Trojans and keyloggers - hack the person, gain access, record their every move or take / do what I need
3) Social Engineering - ask them politely 
4) Get hacking / cracking - too complex to explain
For passwords, network sniffing and keyloggers are the easiest.
At this point I think I'm just blathering. I'll shut up now. 