Home/Modules/antivirus

antivirus

library module lib/antivirus

Examples

lib/examples/antivirus

6 file(s)

<img align="right" src="https://github.com/mearvk/SLeeLa/blob/master/images/debian/debian-logo.png" width="75" height="75" alt="SLeeLa">

SLeeLa Antivirus Components

Status: component framework / integration contracts. This directory defines the SLeeLa-side components for local and system-wide scanning and the ClamAV adapter boundary. It is not yet a complete, active antivirus product: the SLeeLa runtime still needs a trusted filesystem walker, process/daemon bridge, OS event monitor, and platform-specific service installer wired to these contracts.

Goals

Components

FileResponsibility
SLScanRequest.sleelaRequest target, scope, recursion, and limits
SLScanResult.sleelaStructured verdict/result
SLScanPolicy.sleelaScan and safety policy
SLClamAVAdapter.sleelaClamAV executable/daemon integration contract
SLQuarantineManager.sleelaQuarantine workflow contract; disabled by default
SLScannerEngine.sleelaOrchestrates request validation and engine handoff
SLLocalScanner.sleelaUser-scoped entry point
SLSystemScanner.sleelaAdministrator-scoped entry point
SLCreator.sleelaCreator — the attested originating Source of a material artifact
SLControl.sleelaControl — governance that secures change to a material artifact (fail-closed)
SLMaterialClaim.sleelaMaterial — the material claim: the thing, present to its author as its own Source
platforms/OS-brand and OS-name profiles

Creator / Control / Material (syntax 2.5 material)

These three classes give users and developers a first-class way to express the material standing of an antivirus artifact (a definition set, a scanner build, a verdict record), complementing the syntax 2.5 material document marker (see SLEELA.syntax §19). All three are themselves material-marked documents.

Minimal use:

SLCreator creator = new SLCreator();
creator.configure("MEARVK LLC", "International");
creator.attest("2026-10-27");

SLControl control = new SLControl();
control.configure("release-council");

SLMaterialClaim claim = new SLMaterialClaim();
claim.configure("sleelavirin-native-engine", "securing-change");
claim.attributeTo(creator);
claim.governWith(control);
claim.declareMaterial("SHIPPED-2.5");

control.authorize(true);            < securing change deliberately >
claim.admitChange("bump definitions");

OS directory convention

These profiles provide paths and capability hints; they must not infer elevated permissions or silently enable blocking behavior. Package names, daemon sockets, service names, and install locations can differ by release and local configuration, so deployment code should detect and validate them.

ClamAV operating model

  1. Prefer a local clamd daemon with clamdscan for repeated scans.
  2. If no daemon is available, optionally use clamscan for a one-shot scan after checking that the signature database is present and current.
  3. Parse engine exit status and structured output into SLScanResult; distinguish clean, detected, error, timeout, and unsupported outcomes.
  4. Keep daemon sockets local and access-controlled. Never expose ClamAV's unauthenticated TCP socket to untrusted networks.
  5. Treat missing signatures, engine errors, permission errors, and timeouts as unknown/error, never as clean.
  6. Linux on-access support may be supplied by ClamAV's clamonacc where supported and correctly configured. This is a separate optional integration, not a cross-platform feature.

References:

Safety defaults

Implementation boundary

The current .sleela files are baseline-syntax component definitions and contracts. Methods that return NOT_CONNECTED, NOT_IMPLEMENTED, or equivalent status are deliberate: they prevent a stub from being misrepresented as an operating scanner. The next implementation step is a tested native host bridge for filesystem enumeration, process execution without shell interpolation, result parsing, cancellation, and OS-specific service/event integration.

Files 21