the htpasswd on unix/linux is uid:crypted_pw
so i'd use that as default... and a specific option to overwrite that.
or and ident tag for plain
user:{txt}password for example
On 4/12/06, Jeff Trawick <[EMAIL PROTECTED]> wrote:
As long as the default doesn't change *to* crypt/plaintext, nobody is
hurt, right? Or do we support the use of htpasswd/htdbm to build
password files for other applications, which might not use apr-util to
check the user/passwd record? (Those users would need to start
overriding the defaults to make it store in the same format as
before.)
--
~Jorge
