home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
pcboard
/
150_tips.zip
/
MSGS.ZIP
/
QWK.MSG
< prev
next >
Wrap
Text File
|
1993-05-12
|
4KB
|
91 lines
Date: 05-11-93 (11:05) Number: 63055 of 63372 (Refer# 62898)
To: JIM JUSKO
From: DAVID TERRY
Subj: BETA report
Read: 05-11-93 (21:44) Status: PUBLIC MESSAGE
Conf: BETA (6) Read Type: MAIL FROM YOU (R/O) (+)
-> What about adding a security level for the QWK command? I limit my "QWK"
-> door to subscribers only.
Since QWK is the same thing as reading a message it inherits the security level
for reading messages.
In fact, QWK is even more closely related to the R;Z command. The only
difference being that the information is put into a QWK packet instead of just
a text file.
I would encourage your users to make use of QWK ... it'll mean less time spent
on your system by an individual user and more time available to other callers
that want to get online.
Of course, you could always put QWK into your CMD.LST file and then place a
security level requirement on it! In other words, if it's not built right into
v15.0, there is very likely a way to make v15.0 do what you want! <grin>
This is an example of what I mean:
Command Security PPE/MNU File -or- Keystroke Replacement
══════════════ ════════ ═══════════════════════════════════════
1) QWK 30 QWK^M
Now if a user with a security level LESS THAN 30 tries to use the QWK command
PCBoard will inform the user that he does not have sufficient security.
On the other hand, everyone else will then be prompted:
QWK Commands: (D)ownload, (U)pload?
Notice that the above has disabled the ability to simply type QWK D and QWK U.
But there are at least two different ways that we can work around this:
Command Security PPE/MNU File -or- Keystroke Replacement
══════════════ ════════ ═══════════════════════════════════════
1) QWK 30 QWK^M
2) QWKD 30 QWK D^M
3) QWKU 30 QWK U^M
Now tell your callers to use QWK to be prompted for the command, or to use QWKD
for a download or QWKU for an upload.
You could even make it QWK for a download and REP for an upload. The way you
define things in v15.0 is largely up to you.
And here is the second way that you could do it:
Command Security PPE/MNU File -or- Keystroke Replacement
══════════════ ════════ ═══════════════════════════════════════
1) QWK 30 QWK.PPE
Notice that this time we're going to launce a PPE file. That is, a simple
program written using the PPL language, that will reconstruct the caller's QWK
command (to include the D or U and even the protocol letters, etc).
Here is what the PPL would look like:
kbdstuff "QWK;"+tokenstr()+chr(13)
All this PPL really does is stuff the keyboard with the QWK command, a
semi-colon separator, and then the tokens (IF ANY) that the caller may have
supplied when he first issued the QWK command, and finally, a chr(13) is simply
a carriage return.
Finally... you could get even more complex here. Inside your PPL program you
could even have conditional tests to let users use the QWK command only during
certain hours of the day, only if their file ratios are in check, only if their
name is on some kind of list. When you can program, you can do ANYTHING you
want!
So now you've found a several of ways that YOU can add a security level
requirement, even if one is not built right into PCBoard.
-> What about modifying for attachment of files. Like a security needed to do
-> so.
There is no security level for attaching a file. But you could write a PPL
program and attach it to the PCBTEXT prompt that is used to ask the caller for
Editor Commands. Your PPL program could then require certain security levels,
etc.
PCBoard v15.0's flexibility ... just about anything is possible. Have fun!