1. Forum
  2. Fidonet
  3. SYNC SYSOPS

  • whislist: add resume of security violations in sbbsecho log

    From Fernando Toledo@1:103/705 to GitLab issue in main/sbbs on Sat Aug 29 08:24:39 2026
    open https://gitlab.synchro.net/main/sbbs/-/issues/1228

    Currently, the sbbsecho task at the end of the log adds a summary of duplicates/additions.

    Is it possible to also add **security violations**?
    Because, for example, I have to go through the entire log, searching line by line for the errors.

    If I had something like the following, it would help me get a summary of the areas where I need to add links (the missing links) to my areas.ini file, instead of having to parse the entire log to find them.

    ```
    Duplicate: 4 detected in SYNCDATA
    Duplicate: 4 detected in WEATHER
    Duplicate: 1 detected in EC_SUPPORT
    Duplicate: 1 detected in CHAT
    Duplicate: 1 detected in SU.GENERAL
    Duplicate: 1 detected in SU.TALKS
    Duplicate: 1 detected in UFO
    Duplicate: 5 detected in EMERGCOM
    Duplicate: 2 detected in WX_TALK
    Duplicate: 4 detected in R20_BEER
    Duplicate: 1 detected in R20_BEST_OF_FIDONET
    Duplicate: 2 detected in EDGE_ONLINE
    Duplicate: 1 detected in WORDS_WORDS
    Imported: 1 msgs total

    Security Violation: COMM 2:341/66
    Security Violation: PASCAL_LESSONS 1:234/567
    Security Violation: OTHERECHO 2:333/444
    Security Violation: ONEWMORE 4:111/2222
    ```
    etc..

    ![imagen](https://gitlab.synchro.net/-/project/13/uploads/035f8f5a8ebcc0200c21cbf3f71ea763/imagen.png){width=900 height=461}

    Thanks!
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Steven Philley@1:103/705 to GitLab note in main/sbbs on Wed Sep 9 18:22:14 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1228#note_10274

    Verified on Linux against the !730 / `sbbsecho-security-violation-summary` change (built from the matching GitHub tip `d6790e86c`).

    Built `sbbsecho` (Clang 18, RELEASE) and tossed real type-2 packets into a minimal SecureEchomail fixture:

    - Areas `TESTGEN` / `TESTDEB` linked only to `1:100/2`
    - Packets from `1:200/3` with two `AREA:TESTGEN` messages (duplicate pair) plus `1:200/4` with one `AREA:TESTDEB`
    - Mid-run still logs `Security violation - %s not in Area File` for every rejected message
    - End-of-run summary is exactly:
    ```
    Security Violation: TESTGEN 1:200/3
    Security Violation: TESTDEB 1:200/4
    ```
    - Empty inbound (no violations) prints no `Security Violation:` summary lines

    Unique-pair summary, duplicate suppression, quiet empty run, and existing mid-run warnings all look good for #1228 / !730.
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)