Trustux documentation

Trustux answers one question, completely offline: can you trust this signature? It checks that the document was not modified after signing, that the signer is who they claim to be, and that the certificate was valid at the moment of signing.

What it verifies

Integrity

The document was not touched after it was signed — including detection of incremental updates appended after signing. A single changed byte turns the verdict red.

Identity

The certificate chain up to a trusted root (AC Raíz República Argentina preloaded), with the signer’s name, CUIT/CUIL, issuing CA and role extracted.

Validity

Revocation by CRL (offline-first) and OCSP (embedded/provided offline, with opt-in online checks), plus the RFC 3161 time-stamp — evaluated at signing time, not just today.

Standards

PAdES (PDF), XAdES (XML, AFIP/ARCA invoices) and CAdES (CMS .p7m / .p7s) all supported.

The verdict

Every check rolls up into a traffic-light verdict — green (valid), amber (valid with caveats) or red (invalid) — with the supporting detail behind it, and an exportable report you can attach to a file. The CLI prints the same verdict for use in scripts and CI.

Trust store and revocation

Identity is only as good as the roots you trust. Trustux validates the chain up to a configured root, ships the AC Raíz República Argentina preloaded, and lets you edit the trust store per jurisdiction. Revocation is offline-first: CRLs are checked locally, OCSP responses can be embedded or provided offline, and online OCSP is opt-in — so verification works air-gapped.

Integration with Selega

Trustux is also the signature engine inside Selega. It enters as an optional capability, off by default — only the superadmin turns it on (cap_firma). With signing enabled, the verdict feeds Selega’s outcome (legalize / observe / certify signature / deny); with it off, Selega behaves exactly as before.