Add advanced PAdES and long-term signature validation
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 15/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Área
- cryptography, security
Línea de trabajo
No implementation files or tests are named; this issue explicitly says not to implement the epic directly. Start by defining the target PAdES profiles and validation requirements, then split the work into focused child issues. Coordinate with #8335, #8943, #8944, and #8945, with automated regression and interoperability tests as the completion criteria.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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:
- #8335;
- #8943 CSC support;
- #8944 eIDAS trust service interoperability;
- #8945 local and hardware-backed signing.
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.
- Lenguaje dominante
- PHP
- Estrellas
- 838
- Forks
- 171
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 280
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de LibreSign/libresign
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 83/100
LibreSign/libresign#9007 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
backend enhancement php
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LibreSign/libresign#8284 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
LibreSign/libresign#9271 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
backend php
Dificultad 4/5 3-5 días Aptitud para principiantes 53/100
Los mantenedores suelen responder en 1 día
Todos los issues de LibreSign/libresign
Issues similares
-
Issue: ready for confirmation Reported on 2.4.9 Triage: Dev.Experience
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
magento/magento2#41773 · 1 comentario ·
Los mantenedores suelen responder en 5 días
-
[BUG] Add bounds validation for numberOfContestants in TeamsGroup::apiCreate()Posiblemente ocupada @RAJJADHAV10 la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
omegaup/omegaup#10512 · 1 comentario ·
Los mantenedores suelen responder en 5 días
-
documentation good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
sorocharge/sorocharge-php#14 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
filesender/filesender#2898 ·
Los mantenedores suelen responder en 1 día
-
cleanup
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día