You are amazing Joe! I am considering using your patch to modify the
functionality of the passwd, but retaining the old functionality with
a new command called newpasswd. :) I hope this doesn't make you feel
like Charlie Brown trying to kick a field goal while Lucy is holding
the football. I really appreciate that you can come out with such an
excellent patch in one day like you did.
As for documentation, and the FAQ, doesn't David Barr do that? I will
admit, that I have not submitted anything to be added, but might be
able to suggest several paragraphs. :) I might even consider digging
through my old posts and offering some of it as tutorial, HOW-TO, or
documentation for the majordomo-docs list. If I am not part of the
solution, I must be part of the problem, so I will try to avoid
procrastinating and get some useful information submitted ASAP. It
will be hard to avoid injecting my "opinions" though. :)
Dan Liston
"Joe R. Jah" wrote:
>
> On Mon, 27 Aug 2001, Dan Liston wrote:
>
> > Date: Mon, 27 Aug 2001 17:48:07 -0500
> > From: Dan Liston <dliston@netscape.com>
> > To: Joe R. Jah <jjah@cloud.ccsf.cc.ca.us>
> > Cc: hawthorne@cybervpm.com, Majordomo-Users <majordomo-users@GreatCircle.COM>
> > Subject: Re: Master password file was: (Quickie)
> >
> > I had no idea the passwd command had been deprecated. This command
> > still creates/updates the listname.passwd file rather than modifying
> > the listname.config. It is a great tool for using a master password,
> > but it is still much easier for list-owner's to send one simple
> > command than it is to retrieve, modify, return, and re-write the
> > config file just to change a password. The risk of unexpected word
> > wrapping alone should be enough to prevent using the newconfig method
> > of changing a password.
>
> I agree that it is a lot easier to send a one line command than to send an
> entire file; however, that is also true for every other change in the
> configuration. The password is not necessarily the most frequently
> modified piece of information in Majordomo.
>
> > Personally, I would prefer the command to be named newpasswd to fit
> > the schema of newinfo, newintro, and newconfig commands, which write
> > to (listname).info, .intro, and .config respectively. I am not
> > certain, as I am not a majorcool user, but I would be willing to bet
> > that it's password routines also depend on listname.passwd vs.
> > modifying listname.config to update passwords.
>
> Majorcool, uses Majordomo to verify passwords; Majordomo looks both in
> <List>.passwd and <List>.config files for admin_passwd. However,
> Majorcool modifies the admin_passwd in the <List>.config file, not in the
> <List>.passwd file.
>
> > The only place in any of the documentation that I can find
> > "deprecated" is in reference to arguments to the resend script. By
> > documentation, I include FAQ, README, Archives, and source code. I
> > will add however, that .strip, .private, .closed, .auto, and .hidden
> > flag files also still work, but I think the settings in .config
> > override them, and unlike the .passwd file, none of these files hold
> > content.
>
> You are right; the documentation has left a lot to be desired;( I wish
> someone would take up the task of updating the FAQ; any takers?;)
>
> > I have to play around a bit again, but these files may change the
> > default settings of config_parse.pl when creating a new
> > listname.config file if the flag files exist. Deprecated, perhaps.
> > Still useful, definately.
>
> To make it even more useful you can apply the following patch:
>
> ftp://ftp.ccsf.org/majordomo-patches/1.94.5/passwd.0
>
> Here is an excerpt from the patch:
> -----------------------------------8<------------------------------------
> # This patch will change a long deprecated password behavior of Majordomo.
> # When receiving the command "passwd <listname> <oldpass> <newpass>" the
> # patched majordomo will change the admin_passwd in the <List>.config
> # file rather that the <List>.passwd file; it leaves that file only for
> # global usage as a master password file.
> #
> # If you have old lists whose owners rely on <List>.passwd file, make sure
> # to transfer the password to admin_passwd in the <List>.config before
> # doing:
> #
> # rm <List>.passwd; ln -s <master.passwd> <List>.passwd
> -----------------------------------8<------------------------------------
>
> Regards,
>
> Joe
> --
> _/ _/_/_/ _/ ____________ __o
> _/ _/ _/ _/ ______________ _-\<,_
> _/ _/ _/_/_/ _/ _/ ......(_)/ (_)
> _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us
Follow-Ups:
References:
|
|
