This is both a heads-up and a question. When you use Majorcool to change
the list passwd, it changes the passwd in the file listname.passwd.
Is this intended?
I thought this file was meant (or grew) to be used by list admins
overseeing multiple lists, and hence I had symlinked all the list.passwd
files to a central password file. Majorcool inadvertantly can give one of
your list owners rights over all your lists.
Since Majorcool purposefully excludes the list password in the config
file that it displays, I assumed all along that it was modifying the
list.config file when the password was submitted. Additionally, the
Majorcool interface will accept the list password in the config file as
your "old password" and change to the "new password" even if the password
in list.passwd doesn't match.
If I'm not being clear, here's an example.
list.config has
admin_passwd = foo
(This is not displayed by Majorcool.)
The file list.passwd is
bar
The "Change List Password" in Majorcool changes the list.passwd file,
further, it accepts "foo" as verification to change "bar".
Omar
Follow-Ups:
|
|
