PassWord Entry v1.1 ~~~~~~~~~~~~~~~~~~~ For MAX's BBS v1.52 ~~~~~~~~~~~~~~~~~~~ By Greg Fitch ~~~~~~~~~~~~~ --------------------------------------------------------------------- Legal: --------------------------------------------------------------------- This Door is freeware, so if you paid for it then please let me know where you got it from and what you paid. This archive must be as is was when made with the exception of origin text files that may be added. YOU RUN THIS DOOR AT YOUR OWN RISK I EXCEPT NO RESPOSABILITY FOR ANY HARM IT MAY CAUSE AT ALL. The Archive must contain the following files: Doors/ PassWordEntryV1.0.Doc (Your Reading It) PassEnter.Config (The Config File) PassEnter/ PassWordEntryV1.0 (The Door ItSelf) Welcome.text (Ansi To Display On Entry) Enter.text (Ansi To Display On Access) Failed.text (Ansi To Display On Failure) --------------------------------------------------------------------- What it Does: --------------------------------------------------------------------- This door is a security door for Max's BBS and contains features from both SecurityGate and Bouncer, it lets you set up a config file and your own Ansi screens, it looks for the password for the users trying to get through it in the Comment field of Max's user config, they are then asked to enter the password and if they get it right in they go, but if they get it wrong they have two more goes at it, if they just hit return the will be put back to the menu they were on if they fail to enter the correct password after 3 tries they will be shown an Ansi screen then asked if they wish to leave a message to the SysOp if they choose no they will be logged off, if they choose yes they will be able to leave a message then they will be logged off. If they get the password right they will be given another Ansi screen then sent to the menu or what ever you have chosen in the config. You can also set a minimum auto pass level this will let all users over this level go straight in without entering a password "handy for sysops" the door will also write a log file and add to it when ever someone uses it (except auto pass users) the log shows what the user did (hit return and "QUIT", made it into the menu "ENTERED" or got logged off "FAILED". The config file also lets you put in the paths to the data files and log file for the door and put in 2 lines of text for "QUIT" and "FAILED" these are to make it more configurable for you. --------------------------------------------------------------------- Installation: --------------------------------------------------------------------- Easy to do just copy the whole PassEnter directory across to your doors directory and "the config file must be in Doors:". Then add it to your Menus config as a standard door. Eg. Key 34 0 0 10000 Doors:PassEnter/PassWordEntryV1.0 You can also edit the ansi screens to look how you want, but don't forget the screen clearing code at the top and the %Z at the bottom with the exception of the Welcome text (don't put the %Z on this). To let a user have access just enter the password for them into the Comment field of the user editor of Max's you can have one password for all users that have access or a different one for each user (I use their own password) and the entry must look like this: >password< yes you must put the > and the < in or it will not find the password, you can put it any where in the comment field as it will find it even if there is other text in there or even if you are using SecurityGate's #-password-# so you can run these two programs together with no problems. The only other thing is the config file and it looks like this: --------------------------------------------------------------------- 2 35 5000 Greg Fitch 0 Doors:PassEnter/ BBS:LogFiles/ Ok your out of here! Sorry you FAILED logging you off ---------------------------------------------------------------------- The PassWord Entry Door Will Only Look At The First 10 Lines ---------------------------------------------------------------------- What each line is: Line 1 = Menu Function 1-33 Line 2 = The Extra Info for Menu Function. Line 3 = FileName/Name/Dest/Path For Menu Function Line 4 = Minimum automatic pass through level. Line 5 = Name for all messages to go to (USUALY THE SYSOP'S NAME). Line 6 = Section number for messages to go to. Line 7 = Path to ANSI data files (MUST END IN A ":" OR A "/"). Line 8 = Path to log files (MUST END IN A ":" OR A "/"). Line 9 = Text to type if they just hit return to quit. Line 10 = Text to type if they failed to gain access. --------------------------------------------------------------------- you can just edit it in a text editor to match your bbs. --------------------------------------------------------------------- Known Bugs: --------------------------------------------------------------------- May turn BBS screen to the color of workbench but this may be dependent on memory addresses I think as I have a few that do this (ones I didn't write) this can be cured when it happens by clicking the screen to the back then and bringing it to the front again, this is not realy a bug and may be somthing to do with the compiler or librarys if you know what causes this please let me know and I will try to fix it. It has no other bugs that I know of. --------------------------------------------------------------------- History: --------------------------------------------------------------------- V1.1 Added Date and time to the log file. V1.0 First release! --------------------------------------------------------------------- Credits: --------------------------------------------------------------------- Thanks to all the other SysOps that have done up the source codes for Max's BBS as that helped me sort out this one. --------------------------------------------------------------------- Bug Reports: --------------------------------------------------------------------- XyonicS BBS +61-7-808-4806 HOURS 8:30pm - 7:00am 7days XMAXNET 292:363/805.0 MEGANET 929:181/849.0 --------------------------------------------------------------------- If you have an idea for a new door then please let me know and I will see what I can do. Thanks. Greg...