> Perhaps we could implement some kind of alternate crypt() function, one that
> doesn't take so long?
Is this a job for twofish?
> I'm sure some XORs and a little bit of bit rotation
> between characters in the password would be enough. Not as secure as
> crypt(), to be sure, but even a crypt()ed password can be brute-force
Only if the person chooses a poor password. A complete brute force
attack is out of reach of most people, for at least the next couple
> The goal is to have the password in a state where it is not just
I'd like to think the goal is a little higher than that.
This message resent by the firstname.lastname@example.org list server http://www.uClinux.com/
This archive was generated by hypermail 2b30 : Sun Apr 07 2002 - 00:01:34 EST