Skip to content
Snippets Groups Projects
Select Git revision
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • new_user_dat
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

str.cpp

  • Rob Swindell's avatar
    1fbb1743
    Move password quality check logic to new userdat.c function: check_pass() · 1fbb1743
    Rob Swindell authored
    sbbs_t::chkpass() now becomes just a thin wrapper around check_pass() and it
    prints the reason for the failure or calls sbbs_t::trashcan().
    
    I also refactored the code quite a bit: no more copying and uppercasing
    (we have strcasestr() now!) and supports calling with a NULL user_t* as I
    expect will be a use case.
    
    This will allow us to expose the password quality checking algorithm to other
    servers (e.g. the web server) that can be used to create new user accounts
    with passwords that meet our quality bar.
    e.g. via a newly created JS method: system.check_password()
    
    Yes, we have bbs.good_password() already (and that still works fine), but
    can't be used by non-terminal server code.
    1fbb1743
    History
    Move password quality check logic to new userdat.c function: check_pass()
    Rob Swindell authored
    sbbs_t::chkpass() now becomes just a thin wrapper around check_pass() and it
    prints the reason for the failure or calls sbbs_t::trashcan().
    
    I also refactored the code quite a bit: no more copying and uppercasing
    (we have strcasestr() now!) and supports calling with a NULL user_t* as I
    expect will be a use case.
    
    This will allow us to expose the password quality checking algorithm to other
    servers (e.g. the web server) that can be used to create new user accounts
    with passwords that meet our quality bar.
    e.g. via a newly created JS method: system.check_password()
    
    Yes, we have bbs.good_password() already (and that still works fine), but
    can't be used by non-terminal server code.