Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Linux
[Top] [All Lists]

Re: A question about passwords and login/authentication

Subject: Re: A question about passwords and login/authentication
Date: Wed, 16 Mar 2005 10:28:16 +1100
On Tue, 2005-03-15 at 14:53 +0100, Pavol Luptak wrote:
Try blowfish instead MD5

I feel a bit uneasy about using symmetric ciphers (like DES or blowfish)
for password encryption. I'm not a crypto guy, but doesn't this bring
about the whole bloody key management can of worms?

In order to check a supplied plain text password you'd have to have the
encryption key available. This also means that you've got something
important to lose - whoever steals the key can simply decrypt the entire
password store (rather than brute-forcing it).

With hashes (crypt(), MD*, SHA*) all you have to have in order to verify
a plain text password is the algorithm itself.

Wouldn't it be wiser to use asymmetric ciphers, destroy the private key
and just use the public key to encrypt new passwords. The public key
could then be published for anyone to check supplied plain text for
validity, yet no-one could decrypt the cipher text. Just like with
hashes, only without their limitations (and performance).

Cheers
Steffen.

Attachment: signature.asc
Description: This is a digitally signed message part

<Prev in Thread] Current Thread [Next in Thread>