• src/sbbs3/fixsmb.c

    From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Fri Jan 16 14:15:19 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/df722f1000bf100344e0c3a6
    Modified Files:
    src/sbbs3/fixsmb.c
    Log Message:
    Don't report "corrupt message header ID" errors when scanning *.shd file

    ... for non-hyper-allocated message bases.

    Invalid header blocks following the last valid header block of a message
    is an expected case for a self-packing (e.g. mail) message base where
    a new shorter header takes the place of an older longer one that used more blocks.

    The very first header block should always be valid and there shouldn't be any invalid block 'gaps' in a hyper-allocated message base.

    ---
    þ 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 Fri Jan 16 20:44:49 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/94bd2b461945bb3030f43a81
    Modified Files:
    src/sbbs3/fixsmb.c
    Log Message:
    Missed this in last commit, the first header record should be valid

    ---
    þ 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 Sat Jan 17 13:49:33 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/2627d10afe5040c9da0eb4e5
    Modified Files:
    src/sbbs3/fixsmb.c
    Log Message:
    Use the SMBLIB v3.21 auto-unlock feature

    Also ensure that all error paths call exit(1), it looks like I thought perror() would terminate the process at some point.

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