Learn about Centmin Mod LEMP Stack today
Become a Member

Beta Branch move cmsec progress message from check scripts to dispatcher in 140.00beta01

Discussion in 'Centmin Mod Github Commits' started by eva2000, May 9, 2026.

  1. eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    11:32 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    move cmsec progress message from check scripts to dispatcher in 140.00beta01

    The previous progress banner lived inside each check script's begin-checks
    block, which printed only on standalone interactive `./check-cve-*.sh`
    runs. The dmotd SSH-login flow — where users actually see the cursor
    flashing while cmsec iterates verdicts — got nothing because cmsec.sh
    invokes the check scripts with `--json --quiet` (which suppresses say()).
    Move the progress feedback up to the dispatcher so it covers both paths.

    Two new dispatcher progress lines (both stdout-tty gated, suppressed
    under JSON output and when stdout is piped):

    1. cmsec.sh do_run() DMOTD_MODE branch — prints
    "* cmsec: running N kernel CVE check(s), please wait..."
    once before iterating do_one_check_dmotd() so SSH-login users see
    feedback during cold-cache fresh runs.

    2. cmsec.sh do_one_check_full() — prints
    "* cmsec: running <cve-id> check, please wait..."
    before exec'ing the check script for interactive `cmsec check <cve-id>`
    runs.

    Both gated on `[ -t 1 ]` so scripted consumers see no extra output.

    Reverted the previous in-check-script banners (43284 / 43500 / 31431)
    that placed the message in the wrong layer.

    Branch parity with 141.00beta01 (commit 2e3c121a) and 132.00stable;
    tools/cmm-security/ remains byte-identical across all three branches.


    Continue reading...

    140.00beta01 branch