Why don't you, instead of using htpasswd files, use something like mod_auth_pam? If you don't want everyone with an account to access it, you should be able to limit that with a proper "require" statement. But, that would guarantee the passwords would stay in sync since they would both be using the same source.
Cheers, Tanner On 9/22/05, Scott Lundgren <[EMAIL PROTECTED]> wrote: > > What are your suggestions for managing htpasswd entries for individual users? > Ideally, I'd like to keep a user's login passwd in sync with their > htpasswd entry, and do it automagically like samba does it. > > I'm working on setting up a subversion server for my development team, and > while a majority of the repository will be public, write access will be > restricted to members of my development team using subversion's > authorization and Apache2's authentication (htpasswd). > > Because we'll want to see individual commits/writes each user will need to > authenticate seperately. Thus individual enteries in the htpasswd file, > more passwd's for me to maintain, more passwd's for them to remember. > > -- > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ : http://trilug.org/faq/ > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ > TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc > -- Tanner Lovelace clubjuggler at gmail dot com http://wtl.wayfarer.org/ (fieldless) In fess two roundels in pale, a billet fesswise and an increscent, all sable. -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
