Skip to content

Add advanced PAdES and long-term signature validation #8946

Open

Description

@vitormattos

This is a roadmap and funding epic.

Important

Do not implement this epic directly.

This issue is for planning, research and funding of the PAdES and validation capabilities needed by future remote-signing, eIDAS and long-term document workflows.

Implementation should be split into focused child issues after each profile and validation requirement is clearly defined.

Background

External signing changes where the private-key operation happens, but it does not remove the need for correct PDF, CMS and PAdES processing.

Future eIDAS and long-term validation use cases may require stronger signature profiles, timestamps, revocation information and validation evidence.

These capabilities belong in the signing and validation layers, not in CSC, QTSP or hardware-provider integrations.

Goal

Extend LibreSign's PAdES and validation capabilities so that remote and local external signing can use the same standards-compliant document layer.

Areas to evaluate

The roadmap should evaluate and, where required, implement:

  • PAdES baseline profiles;
  • timestamp support;
  • certificate and chain validation;
  • OCSP and CRL handling;
  • embedding validation material for long-term validation;
  • preservation of existing signatures during incremental updates;
  • validation at signing time;
  • long-term validation behavior;
  • interoperability with independent PDF signature validators.

The exact target profiles, including B-B, B-T, B-LT and B-LTA, must be selected based on real use cases and standards requirements before implementation starts.

Why this matters

A remote signature is only useful if the resulting document remains interoperable and verifiable.

Keeping these capabilities in a common PAdES layer means that CSC, eIDAS trust services, HSMs and physical certificates can all reuse the same document implementation.

Business and funding value

Long-lived documents, public-sector workflows, regulated organizations and archival processes often require stronger validation guarantees than a basic digital signature.

Funding this work improves LibreSign for all signing methods, not only one provider or certificate type.

Dependencies

This epic can progress incrementally, but its priorities should be coordinated with:

Out of scope

Provider authentication, credential discovery, OAuth and hardware communication are not part of this epic.

Done when

The selected PAdES profiles and validation requirements are implemented with automated regression and interoperability tests and can be reused by local and remote signing providers.

Activity

  1. changed the title [-][EPIC] Add advanced PAdES and long-term signature validation[/-] [+]Add advanced PAdES and long-term signature validation[/+] on Sep 30, 2026
  2. added theissue type on Sep 30, 2026
  3. no84by commented on Nov 18, 2026

    @no84by

    Concrete child work for this epic, open for review:

    Please attach them as sub-issues if they fit the plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions