Feature Requests item #409071, was opened at 2001-03-16 05:06 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=409071&group_id=103
Category: None Group: None Status: Open >Resolution: Fixed Priority: 5 Submitted By: Karsten Thygesen (karthy) Assigned to: Nobody/Anonymous (nobody) Summary: Crypt/md5 change on the fly Initial Comment: Hi Pr. default, Mailman tries to use crypt if it is available, and if not, it uses md5. Fine. If an installation is using a python without crypt capability, mailman will be using md5, but if the python installation is changed and now supports crypt, mailman fails do validate any passwords. Suggestion: store the encryption method together with the crypted password, so that multiple encryption methods can be used at once. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:40 Message: Logged In: YES user_id=12800 MM2.1 never uses crypt or md5 -- it always uses sha. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=409071&group_id=103 _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
