Hello,

I found a bug concerning the inactivity timer. I have not been able to track down when the timer is being reset correctly (user active) but I am certain that if a user is just browsing the menu's of a system that he will be disconnected after 300 (default) seconds.

Pre-test steps to take:

#--Todo
1. Install fresh system
2. Create account
3. Validate account to sysop
4. Configure the telnet server stuff
5. Set timeout to 180

#---hh:mm:ss - result / command
1. 10:00:00 - telnet to freshly new system
2. 10:00:30 - fill in name and press enter at given time
3. 10:01:00 - fill in password and press enter at given time
4. 10:01:30 - invisible logon (used sysop account) and press N at given time 5. 10:01:45 - e-mail (first time login message) and press N at given time
6. 10:02:00 - main menu is loaded and press M at given time
7. 10:02:30 - message menu is loaded and press Q at given time
8. 10:03:00 - main menu is loaded and press M at given time
9. 10:03:30 - message menu is loaded and press Q at given time
10. 10:04:00 - main menu is loaded and press M at given time
11. 10:04:30 - you are being disconnect now due to inactivity

You can also test it in a system that is full configured, just browse from
main menu to message menu and back ....

Gtx,
sPINOZa

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: -.sOUNDGARDEn.- (21:1/116)

On 09/17/17, sPINOZa said the following...

Hello,

I found a bug concerning the inactivity timer. I have not been able to track down when the timer is being reset correctly (user active) but I
am certain that if a user is just browsing the menu's of a system that
he will be disconnected after 300 (default) seconds.

Thank you for this report and the detailed info that you have provided - appreciated :)

Also, welcome :) It's nice to see a post from your system and I can confirm
it made it all the way to New Zealand... and beyond :)

Best, Paul

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Cryptogenic Radix (21:1/179)

I found a bug concerning the inactivity timer. I have not been able to track down when the timer is being reset correctly (user active) but I
am certain that if a user is just browsing the menu's of a system that
he will be disconnected after 300 (default) seconds.

This is intentional. Users have to actually do something useful in the inactivity timeout window, or they will be logged off.

Otherwise they could just make a script that goes from your main menu to your message menu over and over and over again and tie up all of your nodes to "attack" your system.

So its not a bug, its an anti-troll mechanism.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)