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.
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.
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.
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.
Dan Liston
"Joe R. Jah" wrote:
>
> On Mon, 27 Aug 2001, Dan Liston wrote:
>
> > Date: Mon, 27 Aug 2001 13:50:31 -0500
> > From: Dan Liston <dliston@netscape.com>
> > To: hawthorne@cybervpm.com
> > Cc: Majordomo-Users <majordomo-users@GreatCircle.COM>
> > Subject: Re: Quickie
> >
> > Yes and no. This also depends on whether or not there is a
> > listname.passwd
> > file in the ~majordomo/lists/ directory. If there is, the admin_passwd
> > setting in listname.config should be empty.
>
> The use of listname.passwd file has been deprecated since 1996, but
> unfortunately for backward compatibility it is still possible to have it
> around. If a list has both a listname.passwd and a non-blank admin_passwd
> field in listname.config file the list would have two different valid
> passwords;(
>
> To prevent that:
> Create a "read only" master password file, and symbolically link all your
> listname.password files to it. That will prevent any list owner from
> overwriting their listname.password file, the deprecated practice; they
> will have to use the newconfig command to change their password;)
>
> A side benefit for Majordomo owner is a master password for remote list
> management;)
>
> Regards,
>
> Joe
> --
> _/ _/_/_/ _/ ____________ __o
> _/ _/ _/ _/ ______________ _-\<,_
> _/ _/ _/_/_/ _/ _/ ......(_)/ (_)
> _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us
Follow-Ups:
References:
|
|
