migration concerns changing default hash in htpasswd/htdbm to sha1 for 2.2.x?

[Jeff Trawick]

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.)