And why would it need to? Most HTTP servers support encrypted
passwords using the UNIX crypt() function (this allows you to use the
server's main password file or a separate one). As long as you have
the original password text you can use ANY server-side encryption/
hashing on the password value you like (unlike Digest).
> Frankly, it seems like we're getting some knee-jerk responses.
> This isn't a popularity contest. The results actually have to
OK, so (besides IE5, which just came out) how many existing HTTP
clients support the full range of Digest options in the final HTTP
1.1 draft standard? I bet not many.
Basic has been supported for years...
-- ______________________________________________________________________ Michael Sweet, Easy Software Products email@example.com Printing Software for UNIX http://www.easysw.com