LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Nathan Brindle <[log in to unmask]>
Thu, 19 Jan 1995 20:50:22 EST
text/plain (56 lines)
On Thu, 19 Jan 1995 18:07:16 -0600 Leon D. Wald said:
>
>Unfortunately, the above is not true for my list, perhaps because I have both
>Subscription= Open,Confirm and
>Validate= Yes,Confirm,NoPW
>
>I have tried 2 commands of the form:
>add datarecd [log in to unmask] First M. Last pw=ppppppp
>
>In both cases I, as owner, was prompted to confirm the command. I have not
>yet tried the approach suggested by Norm Aleks involving the command-job
>feature because I wasn't very comfortable with the syntax. I think I'll try
>that next.
 
I don't think I caught that the first time.  The "confirm" parameter in
the Validate= keyword is what is causing your problem.  That parameter
sets the validation level required for commands to LISTSERV.  If Validate=
Yes, it sends the "cookie" validation for all commands.  If Validate= No,
the only command validated is PUT (when you store the list on the server).
If you leave out the Confirm parameter, Validate doesn't send the cookie
validations at all.  Your problem seems to be in the use of the NoPW
parameter, however, because even though you are sending the password,
your instructions to LISTSERV are not to accept the password as valid and
to send the "magic cookie" ("OK") command validation message.
 
Let's take a look at some alternatives:
 
Validate= No      All commands except PUT are taken at face value without
                  validation
 
Validate= Yes     All "protected" commands such as DELETE or ADD require
                  password validation (list password or personal passwords
                  are OK for list owners).
 
Validate= Yes,Confirm  All "protected" commands are validated using the
                  "OK" ("cookie") method by default, although passwords
                   are accepted where appropriate.
 
Validate= Yes,Confirm,NoPW  All protected commands are validated using the
                  "OK" mechanism and passwords are not accepted, since they
                  are not as safe as "cookies".  RECOMMENDED SETTING FOR
                  SECURE LISTS.
 
Validate= All,Confirm
Validate= All,Confirm,NoPW  All commands involving a change in state, except
                            the PUT command are validated using the "OK"
                            mechanism, with or without a password alternative.
 
If you change your Validate= keyword to
 
* Validate= Yes,Confirm
 
I think your list will work the way you want it to.  :)
 
Nathan

ATOM RSS1 RSS2