home *** CD-ROM | disk | FTP | other *** search
-
- ─────────────────────────────────────────────────────────────────────────
-
- ████████ ▄█████ ██▀ ▀██ ██████ ██ ██
- ▀ ██ ▀ ██▀ ▀██ █████▄ ▄███▄ ▄███▄ ██▀ ▀ ██ ██ ██ ▀ ██ ▄██▀
- ██ ██ ██ ██ ▀██ ██▀ ▀██ ██▀ ▀██ ██ ██ ██ ██ ████▀
- ██ ██ ██ ██ ▄██ ██ ▄█▀ ██ ██ ██ ███████ ████ ███
- ██ ██ ██ █████▀ █████▄ ██ ██ ██ ██ ██ ██ ████▄
- ██ ██▄ ▄██ ██ ▐█▌ ██ ▄██ ██▄ ▄██ ██▄ ▄ ██ ██ ██ ▄ ██ ▀██▄
- ▄██▄ ▀███▀ ██▄ ██ █████▀ ▀███▀ ▀█████ ██▄ ▄██ ██████ ██ ██
-
- ─────────────────────────────────────────────────────────────────────────
- Version 2.10a
- By Steve Blinch of Mikerosoft Productions
- ─────────────────────────────────────────────────────────────────────────
-
- ─────────────────────────────────────────────────────────────────────────
- Intro
- ─────────────────────────────────────────────────────────────────────────
-
- TurboCHEK is a callback verification system designed to ensure
- BBS security. The idea is that if a user is using a fake phone
- number, he won't be able to get access to your BBS, and cause any
- problems there -- and if he's using his REAL phone number and causing
- problems, even under a fake name, it's not too difficult to find out
- his REAL name, and take actions against him/her. TurboCHEK also stops
- users from using more than one username on your BBS, as it will auto-
- matically search your userbase for duplicate phone numbers.
-
- ─────────────────────────────────────────────────────────────────────────
- TurboCHEK Warranty/disclaimer
- ─────────────────────────────────────────────────────────────────────────
-
- Prior to it's release, TurboCHEK was tested on an IBM '486/33,
- '386/33, '386/20, and a '286/12. We found no errors, and TurboCHEK
- successfully called back every user that we tried it on. What we're
- trying to say is that it works just great for us.
- But, there IS the possibility that it might not work for you.
- So, if you use it, and it doesn't perform as well as it did on our
- systems, you take full responsibility for anything that happens,
- including any problems or damages that may occur due to the use of it.
- In no event shall Mikerosoft Productions, Steve Blinch, Michael
- Helliker, or any other member of our crew be liable to you or anyone
- else for any damages or costs, including, but not limited to, any
- lost profits, lost savings, lost income, lost information, loss of the
- ability to use TurboCHEK, or other incidental or consequential damages
- arising out of the use or inability to use TurboCHEK.
-
- ─────────────────────────────────────────────────────────────────────────
- Configuring TurboCHEK
- ─────────────────────────────────────────────────────────────────────────
-
- TurboCHEK now comes with a setup program, TCSETUP.EXE, as opposed
- to the old .CTL file method of configuration. Since some of the items
- in the configuration might be a bit obscure, here they are explained a
- bit more clearly:
-
- Main Menu
- ══════════════════════════════════════════════════════════════════════
-
- BBS Software
- ──────────────
- Not too difficult -- The BBS software that you're running: SuperBBS
- or RemoteAccess.
-
- BBS Path
- ──────────────
- The full path to your BBS files (USERS.BBS, TRASHCAN.CTL, etc). In
- a multinode system, this would be your common path.
-
- Log Style
- ──────────────
- How should TurboCHEK write to your log file: SuperBBS style,
- RemoteAccess Compact, or RemoteAccess Expanded.
-
- Log Filename
- ──────────────
- The name of your log file. This is written to either the BBS path
- (in a single node system) or the node directory (in a multinode
- system).
-
- Bad Phone Number Handling
- ───────────────────────────
- If a user has a phone number which you have placed in the bad phone
- numbers list, what action should be taken?
-
- a) Return to the BBS
- b) Hang up on user
- c) Put the user's name in the TRASHCAN.CTL file in your BBS direc-
- tory (or common directory) & hangup, therefore locking his/her
- username out of your BBS.
-
- Dupe Phone Number Handling
- ────────────────────────────
- If a user has a phone number which is already being used by another
- user on your BBS, what action should be taken?
-
- a) Return to the BBS
- b) Hang up on user
- c) Put the user's name in the TRASHCAN.CTL file in your BBS direc-
- tory (or common directory) & hangup, therefore locking his/her
- username out of your BBS.
-
- Dialing Menu
- ══════════════════════════════════════════════════════════════════════
-
- Delay Before Dial
- ───────────────────
- After disconnecting, some modems require a pause of a second or two
- to recuperate. That's what this number is for.
-
- Wait for Connect
- ──────────────────
- After dialing the number, how long should TurboCHEK sit there and
- wait patiently for a connection?
-
- Dial Attempts
- ───────────────
- How many times should TurboCHEK dial the user's phone number and
- wait for a connect if it does not connect on the first attempt?
-
- Number Menu
- ══════════════════════════════════════════════════════════════════════
-
- Local Area Code
- ─────────────────
- Your area code, the one people have to dial when they're calling
- you long distance (i.e. in ###-xxx-xxxx and (###) xxx-xxxx, ### is
- the area code).
-
- Local Prefixes
- ────────────────
- A dial prefix is the first 3 digits of a seven-digit phone number,
- i.e. in xxx-###-xxxx and (xxx) ###-xxxx, ### is the prefix. If you
- can find ALL the dial prefixes which are local to you, and enter
- them into TurboCHEK's setup, TurboCHEK will be able to tell auto-
- matically who is a long distance caller and who is not (using the
- area code as well) and decide whether or not to call the user back.
- If you cannot find out all of the prefixes, or there are too many
- to enter, this option can be disabled and the user will simply be
- asked whether or not he is long distance. (Don't worry, if the
- user lies, it still won't cost you anything as the call won't go
- through anyway, without the 1- in front of it!)
-
- The defaults are for Abbotsford, B.C., Canada.
-
- Bad Phone Numbers
- ───────────────────
- If you want to avoid a certain user, enter his phone number here.
- When he calls, he will not be verified, and an action will be taken
- (he will either be returned to the BBS, hung up on, or locked out,
- depending on what option you chose back in the Main Menu).
-
- Toggle Menu
- ══════════════════════════════════════════════════════════════════════
-
- Save Password In Comment Field
- ────────────────────────────────
- As a security feature in RemoteAccess, the makers decided it would
- be a good idea to lock up the users' passwords nice and tight.
- Notice how you can NEVER see the users' passwords in RAMGR? Due to
- interest by SysOps in their users' passwords, I've added this
- option which puts the user's password in the comment field, there-
- fore allowing the SysOp to view it thru RAMGR. Of course, this is
- of no benefit to SBBS users, but hey, they should switch to RA any-
- way!! :-)
-
- Check Dupe Numbers
- ────────────────────
- Should TurboCHEK check to see if the user's phone number(s) is/are
- already in use? This is useful in case the user changes his phone
- number just before verification, but after logging on.
-
- Verify Long Distance Users
- ────────────────────────────
- Only use this if you're rich! If this is enabled, TurboCHEK will
- place long distance phone calls (charged to YOU) to verify long
- distance users. It is *NOT* recommended that you enable this
- option, for obvious reasons!
-
- Ask User If He/She Is Calling Long Distance
- ─────────────────────────────────────────────
- If there are too many dial prefixes for your calling area, or you
- just don't feel like typing them in, just enable this option.
- TurboCHEK will then ask the user whether or not he/she is calling
- long distance.
-
- Color Menu
- ══════════════════════════════════════════════════════════════════════
-
- Bar Color
- ───────────
- The color of the boxes & a few other things.
-
- Prompt Color
- ──────────────
- The color of prompts, menu items, etc.
-
- Text Color
- ────────────
- The color of variable text (username, phone numbers, etc.) & inst-
- ructions given to the user.
-
- Hilite Color
- ──────────────
- The color of text used to point out specific information.
-
- ─────────────────────────────────────────────────────────────────────────
- Setting up TurboCHEK for use with RA and SuperBBS
- ─────────────────────────────────────────────────────────────────────────
-
- Create a batch file containing the following:
-
- @Echo Off
- CD\RA\TCHEK
- TCHEK.EXE [parameters]
- CD\RA
-
- [parameters] would be one or more of the following:
-
- /N? Specify node number, ? is the number itself
- /P<path> Specify node directory (for EXITINFO.BBS, etc.)
- /1 By default, TurboCHEK reads DORINFO?.DEF, where ?
- is the node number -- using /1 forces DORINFO1.DEF
- no matter what node the user is on
- /! Read DOOR.SYS instead of DORINFO?.DEF
- /S??? Multitaskers: Release timeslice every ???/100 of a second
- /O Do not verify user, only ask password (intended for RA
- SysOps to get their users' passwords into the comment
- field, even if the user has already been verified).
- /Fxyz Only works with /O parameter, sets a certain flag if the
- user enters the correct password. "x" is the flag letter
- (A, B, C, or D), "y" is the flag number (1 to 8), and "z"
- is the status (- or X). See section below explaining this.
-
- (when using parameters, "-" or "/" can be used, it doesn't matter)
-
- We used the following menu items when testing TurboCHEK:
-
- RemoteAccess [tested under version 2.02]
-
- Type: 7
- Data: *C /C D:\RA\TCHEK\TCHEK.BAT *N
- (You may need to add a *M at the end if you run outta memory!)
-
- SuperBBS [tested under version 1.17-3]
-
- Type: 7
- Data: *C /C D:\SBBS\TCHEK\TCHEK.BAT *N *E
- (You may need to add a *S at the end if you run outta memory!)
-
- Concord [tested under version O.O1-G]
-
- Type: Run External Program
- Data: *C /C D:\CONCORD\TCHEK\TCHEK.BAT *N *D2- *D3-
- (You may need to add a *S<minmemkb> at the end if you run outta
- memory!)
-
- ─────────────────────────────────────────────────────────────────────────
- RA: Password-To-Comment Field, users who have already been verified
- ─────────────────────────────────────────────────────────────────────────
-
- If you're using RA, and just switching to TurboCHEK, you probably have
- several (hundred?) users verified already. Rather than force each one
- to use the CBV again, you can do the following to ask the password ONLY
- and place it in the user's comment field, NO callback required:
-
- In Your Batch File (D:\RA\TCHEK\TCHEKPWD.BAT)
-
- @Echo Off
- CD\RA\TCHEK
- TCHEK -PD:\RA\NODE%1 -N%1 -O -FC8X
-
- In Your Menu (preferrably the first option in the TOP menu)
-
- Type: 7
- Data: *C /C D:\RA\TCHEK\TCHEKPWD.BAT *N
- Flag: Flag C8 *MUST* be set to "O" (i.e. C might be "-------O")
-
- This way, if RA sees that flag C8 is NOT set, TurboCHEK will be run and
- the user will have to enter his/her password. If he/she enters the
- correct password, flag C8 will be set, therefore stopping TurboCHEK
- from being run again.
-
- This might seem complicated, and if it does, don't worry... Just set
- everything up as shown here and it'll work just fine!
-
- *NOTE* C8 is just an example, you can use any flag you want, but which
- ever one you use MUST be set to "-" for every user in the user-
- base!
-
- ─────────────────────────────────────────────────────────────────────────
- Version History
- ─────────────────────────────────────────────────────────────────────────
-
- [2.10a] ■ Added Concord support
- ■ Added password-to-comment option for RA
- ■ Setup program, TCSETUP.EXE now added
- ■ Text control file TCHEK.CTL replaced with binary TCHEK.CFG
- ■ Added specific bad number & dupe number consequences (Return to
- BBS, Hang up, or Lockout user)
- ■ Bad fone number check now checks both voice & data, not just
- the one that the user chooses to call back at
- ■ Added file sharing (nasty share violations started to annoy
- me! :-))
- ■ Added dupe fone number check
- ■ Got rid of DDI support.. 'twas a good idea, but it was just too
- damned hard to use :-)
- ■ Did some internal stuff... fixed a few cosmetic errors... and
- a bunch of other little buglets... :-)
- ■ Fixed bug in which xxxyyyy style phone numbers were formatted
- as xxx-yyy-y
- ■ Fixed bug in which long distance verification would not work
- even if the SysOp configured it to!
- ■ TurboCHEK no longer dials the area code before the phone num-
- ber, except in long distance calls
- ■ Fixed bug in which 1- phone numbers would not be handled
- ■ Added new codeword file TCHEK.CWD, from which all the user
- codewords will be read (if file exists, that is)
- ■ Fixed bug with REALLY long user-locations & most SuperBBS
- phone numbers being shown incorrectly
- [2.00a] ■ Due to WAY too many bugs & problems (not to mention losing
- the source code!), I decided to completely rewrite this
- version from scratch. Everything's new, and should work MUCH
- better than the previous versions!!
- [1.00b] ■ Never released this sucker to the public -- the only one to
- get it was Mikerosoft BBS!
- [1.00a] ■ Fixed bug where TurboCHEK would not call the user back again
- if he was not reached on the first call
- ■ Many previous versions were created, however, none of them
- worked... this does, though... <for us, at least!>
-
- ─────────────────────────────────────────────────────────────────────────
- End of TCHEK.DOC
- ─────────────────────────────────────────────────────────────────────────
-