• src/sbbs3/main.cpp sbbs_ini.c src/sbbs3/scfg/scfgsrvr.c src/sbbs3/star

    From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Wed Nov 22 20:44:29 2023
    https://gitlab.synchro.net/main/sbbs/-/commit/a335dd5acde650e6093d73f9
    Modified Files:
    src/sbbs3/main.cpp sbbs_ini.c src/sbbs3/scfg/scfgsrvr.c src/sbbs3/startup.h
    Log Message:
    Support configurable max-severity for all SSH-related log messages

    Default: Warning

    I'm tired of SSH-related errors that I can't do anything about, filling
    my error.log file and mail inbox.

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Wed Nov 13 19:49:03 2024
    https://gitlab.synchro.net/main/sbbs/-/commit/c226475c2920fe8992b5ac02
    Modified Files:
    src/sbbs3/main.cpp sbbs_ini.c src/sbbs3/scfg/scfgsrvr.c src/sbbs3/startup.h
    Log Message:
    Allow a separate log level for the event thread of the terminal server

    So you want to debug (timed) events, but don't want to get debug-spew in your terminal server log output? Now you can: By default, the event thread log
    level will be the same as the terminal server, but now you can override this
    by setting [BBS] EventLogLevel in the sbbs.ini file or set it in SCFG->Servers->Terminal Server->Event Log Level.

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Sun May 17 19:31:59 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/eda8869d558df31fcbb72e77
    Modified Files:
    src/sbbs3/main.cpp sbbs_ini.c src/sbbs3/scfg/scfgsrvr.c src/sbbs3/startup.h
    Log Message:
    sbbs: optional ip-silent.can target for max-concurrent auto-filter (issue #1140)

    New per-server setting `MaxConConnFilterSilent` (sbbs.ini [bbs] section,
    SCFG: Servers -> Telnet/RLogin -> Max Concurrent Connections -> Auto-Filter Silently). When enabled, IPs that exceed the concurrent-connection
    threshold are added to `text/ip-silent.can` instead of `text/ip.can`, so subsequent connections from those IPs are dropped without logging a
    "blocked" notice. Default is `false` (unchanged behavior).

    Also log the basename of the .can file the abuser IP is being added to ("BLOCKING IP ADDRESS: <ip> in <ip.can|ip-silent.can>") matching the
    mailsrvr spam_block precedent.

    Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net