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.)
- migration concerns changing default hash in htpasswd/htdbm... Jeff Trawick
- Re: migration concerns changing default hash in htpas... Jorge Schrauwen