User Guide

Document recipient (no account)

You do not need an account to verify a document.

1. Open https://host.name.my/verify.
2. PDF: upload the PDF. Other files (DOCX/XLSX/PNG/ZIP): upload the original and the .p7s file.
3. Click Verify. A VALID result means the document is authentic and unchanged.

Signer

1. Log in and make sure you have an active certificate (ask your CA Admin if not).
2. Go to Documents → + Upload.
3. Choose a title & file (max 64 MB), click Upload.
4. Click Sign now.
5. Download: PDF → one signed file. Other files → original + .p7s.
6. Share the verify link with the recipient.

Upload options: second signer (multi-signer), reason/location, stamp label & colour, and supersedes a previous version.

Multi-signer: the document is complete only when every signer has signed. Invite via the /sign/<token> link (shown to the owner and emailed).

Bulk: select several unsigned PDFs on the Documents list and click Sign selected.

DRAF watermark: an unsigned PDF downloads with a DRAF watermark; it disappears once signed.

Best practice: sign the final file only. Any edit after signing makes the signature invalid.

Non-PDF files (Word, Excel, images, ZIP)

1. Upload the file and click Sign now.
2. Download both: the original file and the .p7s signature.
3. Send both files to the recipient.
4. The recipient verifies at /verify by uploading both.

Word/Excel does not show the signature inside the document. That is normal — the signature is the separate .p7s file, not a visible stamp.

A hash match on the public record (/d/<token>) only proves the file is unchanged. It is not signature verification — use the Verify page with the .p7s for that.

Public record & revocation

Every document has a public record at /d/<token> (link & QR on the stamp). Anyone can check a file against the registered hash (MATCH / NO MATCH).

The owner/admin can withdraw a document; the verifier then reports it as revoked (withdrawn). A document can also be marked as superseded by a newer version.

Administrator (CA Admin / Super Admin)

• Users → + New user: add users (signer/verifier/auditor/ca_admin).
• Issue new certificate: on the user page; the system generates the keypair + certificate and stores the key encrypted.
• Revoke certificate: the CRL is regenerated automatically.
• CA page: Root/Issuing CA status, download root-ca.crt, regenerate CRL.
• Backup: automatic daily (cron 03:15) to /root/backups/pki (encrypted).

Auditor

The Audit page lists every action with a Hash chain: VALID / BROKEN indicator. If BROKEN, records may have been altered outside the system — investigate.

Benefits

Trust model & limits

• Private CA — recipients import the root once; not recognised by public trust stores.
• Timestamps are embedded in the PDF signature (PAdES-B-T), issued by our own TSA.
• Revocation is via CRL and OCSP (/ca/ocsp). Documents can be withdrawn.
• Long-term validation (LTV/DSS) is not supported.
• Upload limit: 64 MB.

FAQ

Preview on Mac does not validate?

Correct — Preview does not check crypto. Use the Verify page or Acrobat.

Acrobat says "validity unknown"?

Import root-ca.crt (and issuing-ca.crt) into trusted certificates.

Cannot sign?

Make sure you have an active certificate and a verified email.

Non-PDF files: what to send?

Two files: the original and the .p7s signature. Without the .p7s there is no signature, and Word/Excel does not display it.

Glossary