-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Does XignAll upload my documents to a server? No. All processing happens locally on your machine. Documents never leave your environment. The only network requests XignAll makes are: license validation (periodic, no document data), TSA timestamp (optional, sends a hash — not the document), and Telegram bot (transmits only the file you explicitly send).
Is XignAll free? Yes — a free edition with no time limit is available for Windows, macOS, and Linux. The free edition covers individual signing with PKCS#12 certificates. PRO and Server Edition unlock additional features. See pricing.
What platforms does XignAll support? Windows 10/11 (x64), macOS (Apple Silicon + Intel, universal binary), Linux Ubuntu 22.04+ (x86_64 AppImage).
Does XignAll work offline / on air-gapped computers? Yes. No internet connection is required for signing. The license includes a 30-day offline grace period, suitable for classified or isolated environments.
What signature format does XignAll produce? PAdES (PDF Advanced Electronic Signatures), compliant with ETSI EN 319 132 and the eIDAS regulation. Accepted by courts, public institutions, notary offices, and government agencies across all EU member states.
Can I produce a Qualified Electronic Signature (QES)? Yes, if you use a qualified certificate issued by a trust service provider listed in an EU Trusted List, stored on a qualified hardware token (PKCS#11). XignAll applies the signature; the qualified status comes from the certificate, not the software.
Can XignAll sign documents that already have signatures from other signers? Yes. XignAll uses incremental PDF updates — the new signature is appended without modifying existing content. All previous signatures remain valid.
Can I sign only specific pages?
Yes. Per signer profile: all pages, even/odd pages, or a custom range (e.g. 1,3,5–8).
What hardware tokens are supported? Any PKCS#11-compliant device: SafeNet/Thales eToken, SafeNet iKey, Gemalto IDPrime, OpenSC-compatible smart cards. Requires the token's PKCS#11 library/driver to be installed.
Is the PIN stored anywhere? No. The PIN is entered once per session and kept in memory only. It is never written to disk.
What input formats does the Pipeline support?
.doc, .docx, .odt, .rtf, .txt, .html, .xlsx, .xls, .ods, .csv. Requires LibreOffice installed.
Is LibreOffice mandatory? Only for document conversion (Pipeline tab and Telegram bot with non-PDF input). If you only sign existing PDFs, LibreOffice is not needed.
How does the Telegram bot signing work? User sends any supported file to the bot in Telegram. XignAll receives it, converts to PDF if needed, signs with the configured SEAL profile, and returns the signed PDF — typically within seconds. See Telegram-Bot-Setup.
What is a SEAL? An electronic seal (eSeal) is an organizational signature — applied by the organization itself, not an individual. In the eIDAS framework, it certifies the document's origin and integrity. XignAll applies the SEAL using a designated PKCS#12 or PKCS#11 profile configured in the Server Edition settings.
Can multiple departments use separate signed output folders?
Yes. The folder watch monitors /SEAL/ and its first-level subfolders independently. Each subfolder gets its own Signed/ and Failed/ output.
Which signing library does XignAll use? pyhanko — open-source Python library for PDF signing and validation.
Can I verify signatures produced by XignAll in Adobe Acrobat? Yes. PAdES signatures are a standard PDF signature format. Adobe Acrobat Reader, Foxit, and any eIDAS-compliant PDF validator can verify them.
What happens if XignAll crashes during batch signing? XignAll uses atomic file writes — each signed PDF is written to a temporary file first, then renamed. A crash leaves at most one incomplete temp file, which is cleaned up on next launch. Already-signed files in the batch are not re-processed.