Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Apache: Dev

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

 

 

Apache dev RSS feed   Index | Next | Previous | View Threaded


trawick at gmail

Apr 12, 2006, 4:11 AM

Post #1 of 2 (514 views)
Permalink
migration concerns changing default hash in htpasswd/htdbm to sha1 for 2.2.x?

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.schrauwen at gmail

Apr 12, 2006, 5:50 AM

Post #2 of 2 (459 views)
Permalink
Re: migration concerns changing default hash in htpasswd/htdbm to sha1 for 2.2.x? [In reply to]

if i understands wrowe's explanation correctly...
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 <trawick[at]gmail.com> 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

Apache dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.