Skip to content
  • rswindell's avatar
    2efd7067
    As PSI-Jack pointed out, detecting fast-logons in login.js does not help · 2efd7067
    rswindell authored
    with logins via SSH or RLogin (handled in answer.cpp). So revert login.js
    back to rev 1.17 since the fast-logons are now detected in the login name
    parsing in login.cpp's sbbs_t::parse_login() which is used in answer() and
    login() - called via bbs.login().
    
    So... if you're writing a login matrix or custom login module where you want
    to use a *different* method of detecting/enabling fast logon support, you'll
    just need to set the SS_FASTLOGON flag in the JS bbs.sys_status property:
        bbs.sys_status |= SS_FASTLOGON;
    
    This also means that 2 modopts.ini options (fast_logon and
    fast_logon_requirments) are now used in logon.js, not login.js, so the section
    where you add them is now [logon], not [login]. Got it? Good. :-)
    2efd7067
    As PSI-Jack pointed out, detecting fast-logons in login.js does not help
    rswindell authored
    with logins via SSH or RLogin (handled in answer.cpp). So revert login.js
    back to rev 1.17 since the fast-logons are now detected in the login name
    parsing in login.cpp's sbbs_t::parse_login() which is used in answer() and
    login() - called via bbs.login().
    
    So... if you're writing a login matrix or custom login module where you want
    to use a *different* method of detecting/enabling fast logon support, you'll
    just need to set the SS_FASTLOGON flag in the JS bbs.sys_status property:
        bbs.sys_status |= SS_FASTLOGON;
    
    This also means that 2 modopts.ini options (fast_logon and
    fast_logon_requirments) are now used in logon.js, not login.js, so the section
    where you add them is now [logon], not [login]. Got it? Good. :-)
Loading