@database MenuPass.GUIDE @node main "Menupass v1.0" MenuPass 1.0 ------------ @{" What is it? " link "whatisit"} @{" Requirements? " link "requirements"} @{" Installation? " link "installation"} @{" Logging? " link "logging"} @{" Bugs? " link "bugs"} @{" Thanx " link "thanx"} @{" Contacting the author/getting updates " link "author"} L8r MF @endnode @node "whatisit" "What is it?" What is it? ----------- Menupass is an excellent addition for security on MaxsBBS systems. It password protects menus. You may want this to password protect sysop menus, adults only sections etc. Ofcourse, without this most people wouldn't be able to access these menus anyway, but sometime users are accidently given the wrong access level [I was once accidently given pornography access =)] and if this program was also used, they would still need a password to access this area. Menupass can also log failed password attempts [Incase you accidently gave a user the wrong access and they tried to guess the password] and can also log ALL entries [Incase you think someone may know the password when they shouldn't]. @endnode @node "requirements" "Requirements?" Requirements? ------------- -Should work fine on 1.3 systems because no special features are used, but will definately work on 2.0+ -MaxsBBS @endnode @node "installation" "Installation?" Installation? ------------- Easy! First copy Menupass to Doors:. Then go to the menu setup in MaxsBBS. Where you used to have Maxs automatically go to a menu using function 2, replace that with function 34, and in the filename menu, put doors:menupass, followed by a space, the menu to go to,the flag, and the password for this menu. So, basically, it should look like this: Doors:Menupass (See @{"LOGGING" link "logging"} for flags). NOTE: The password must @{b}NOT@{ub} include any flags! This includes spaces, -'s and ='s (See @{"LOGGING" link "logging"})! The password @{b}IS@{ub} case sensitive! EG: Before: Key: Function: Extra: Lo acc: Hi acc: filename: S 2 50 1000 10000 After: Key: Function: Extra: Lo acc: Hi acc: filename: S 34 0 1000 10000 doors:menupass 50 password So what will actually happen is when a user presses S, it will ask for the password (In this case the password is "password") and if correct, it will go to menu 50. Don't worry about normal low/high access stuff, that will still work if you leave in the lo/hi access on the menu, just that now you will need that access level to access the door to access the menu, not just to access the menu. @endnode @node "logging" "Logging?" Logging? -------- A good feature of Menupass is that it can log what's been going on. The current flags are as follows: No logging - Log only failed attempts = Log all entries EG: No logging: Doors:Menupass 50 password Log failed attempts: Doors:menupass 50-password Log all entries: Doors:menupass 50=password The logfile for failed attempts will look like this: Joe Blogs - passwd Joe Blogs - Ineedthepassword Guest - hmmmm Etc... The logfile for all entries will look like this: Joe Blogs - passwd Joe Blogs - Ineedthepassword Guest - hmmmm Midnight Flip - password (Correct password) Etc... You may be wondering why you would need to log all entries. The reason I've got that feature incase you think some users may have the password and you haven't given it to them. @endnode @node "bugs" "Bugs?" Bugs? ----- I have recently had bug reports in another doors I made. the problem was that when run on two nodes, it crashed. This only happens if you local log in on two nodes and run the same door. This was because when you usually run a door, MaxsBBS tells the door what node it was run from, but when you local log in, the node is actually 0, not the dial up node number (such as 1 or 2). Then it crashes because both doors are trying to write to the same node number. If you don't understand this, then make sure you don't run a the same door twice on two LOCAL login nodes (remote ones are fine). If you find any other bugs, please contact me! @endnode @node "thanx" "Thanx" Thanks: ------- Many thanks to: Randy Quick, since I used his basic door starter, and minor help (one command =) along the way Surge, for beta testing @endnode @node "author" "Contacting the author/getting updates" Contacting the author/getting updates: -------------------------------------- I can be contacted on the following BBS's: Surge BBS (+61 8 8384 3788 time: CST 9pm to 7am) Freds BBS (+61 8 8341 5944) Note: you must know my REAL name =) I am ofcourse on other BBS's, but these are the ones I am on the most. You can email me at: mflip@ozemail.com.au Updates to this program (if any) and other programs I have written can be obtained from my homepage: http://www.ozemail.com.au/~mflip (I once accidently missed of the /~mflip in another doc for another door that I wrote, but this is the correct address) @endnode