Autofirma 1.7.2 [ DELUXE FIX ]

AutoFirma 1.7.2: The Latest Update to Spain’s Official Electronic Signature Client

Madrid, Spain – The Spanish government’s technological body, Secretaría General de Administración Digital (SGAD), has rolled out version 1.7.2 of AutoFirma, the country’s flagship desktop application for electronic signatures. This maintenance update reinforces the software’s role as a critical tool for citizens and businesses interacting with public administrations.

AutoFirma allows users to sign documents (PDF, XML, etc.) using digital certificates stored on local hardware—such as the DNIe (Spanish electronic ID), cryptographic smart cards, or USB tokens—without needing a remote server. autofirma 1.7.2

Roadmap and Future Outlook

The SGAD team has indicated that AutoFirma 2.0 is under early development, focusing on: AutoFirma 1

• A modernized UI (Qt or JavaFX, replacing Swing)
• Cloud certificate support (without local hardware)
• REST API for server-side automation

However, no official release date has been announced. Until then, version 1.7.2 remains the stable, production-ready standard for electronic signing across Spain’s public sector. A modernized UI (Qt or JavaFX, replacing Swing)

Notable fixes and behavior changes

• Resolved intermittent crashes when enumerating PKCS#11 providers on some Linux distributions.
• Fixed an issue where signing large PDF files could hang or consume excessive memory.
• Corrected incorrect timestamping behavior when external TSA servers returned certain time formats.
• Improved detection and import of certificates from Windows certificate store.
• Patched handling of certain ASN.1 structures that could cause signature validation to fail.
• Updated bundled libraries (cryptographic and parsing) to recent stable releases to address known CVEs.

Security recommendations

• Keep the underlying Java runtime updated with security patches.
• Use up-to-date smartcard/token middleware and firmware.
• Validate signatures and certificate chains using trusted root stores.
• Restrict file sources and avoid signing untrusted or malformed documents.