At 04:32PM 12/31/96 -0600, Paul Opie wrote:
>by changing $list.pass to $list.passwd in config_parse.pl, as above, i
>achieve my goal of changing what the <list>.config file says the password
>file name should be. i'll demonstrate:
>
>before the change (config_parse.pl contains: $list.pass)
>========================================================
> # approve_passwd [word] (t2.pass) <resend>
> # Password to be used in the approved header to allow posting to
> # moderated list, or to bypass resend checks.
>approve_passwd = t2.pass
>
>after the change (config_parse.pl contains: $list.passwd)
>=========================================================
> # approve_passwd [word] (test2.passwd) <resend>
> # Password to be used in the approved header to allow posting to
> # moderated list, or to bypass resend checks.
>approve_passwd = test2.passwd
>
>[both of the above paragraphs were constructed by MD.]
Yes, and nowhere does it say the .pass thing is a FILENAME.
It is a literal string.
>what i wanted to do was change what is written in the config file because
>in it's distributed state, config_parse.pl does not build a new
><list>.config file with the proper extention, if one happens to be using
>the password file. (proper being what the rest of MD is searching for)
You're not lsitening.
The value in the .config file IS USED AS A PASSWORD. It is NOT OPENED
AS A FILENAME by any majordomo code.
You put passwords in the .passwd file and/or the .config file. YOU DO
NOT PUT FILENAMES IN THE ARGUMENTS TO approve_passwd.
--
ROGER B.A. KLORESE rogerk@QueerNet.ORG
2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF
"There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick
|
|
