Repository navigation
Description
This is a roadmap and funding epic.
Important
Do not implement this epic directly.
This issue defines the future direction for physical certificates, tokens, smart cards and other local or hardware-backed signing methods.
Implementation should happen later through focused child issues after the external-signing foundation is stable.
Background
The architecture in #8335 separates PDF/PAdES processing from the operation that uses the private key.
That same model should allow LibreSign to support certificates whose private keys are stored on a local device or hardware module.
The PDF/PAdES implementation should not be rewritten for each hardware type.
Goal
Allow LibreSign to use signing keys that remain in local or hardware-backed devices.
Possible targets include:
- smart cards;
- USB cryptographic tokens;
- PKCS#11 devices;
- HSMs;
- native OS certificate stores where appropriate.
Architecture direction
The expected lifecycle remains:
- LibreSign prepares the signature;
- a local or hardware integration signs the prepared data;
- LibreSign receives the signature value;
- LibreSign finalizes the PDF/PAdES signature.
The device integration should not need to understand PDF internals.
Depending on the environment, communication may require:
- PKCS#11;
- a native helper;
- a browser extension;
- a local bridge;
- platform-specific certificate APIs.
These transport decisions should be isolated from the signing engine.
Why this matters
Many organizations already own certificates on smart cards, tokens or HSMs.
Supporting them without exporting the private key would let LibreSign work with existing security infrastructure and regulated certificate ecosystems.
The same foundation can support both European and non-European certificate systems.
Business and funding value
This work is relevant to organizations that cannot move private keys into LibreSign or into a cloud provider.
Potential funders include organizations using corporate HSMs, public-sector certificate infrastructures, certificate authorities and organizations that depend on smart-card or token-based signatures.
Dependencies
This epic depends on #8335.
Some implementations may also reuse the generic provider/session concepts from #8942, but local-device transport must remain independent from remote provider APIs.
Out of scope
This epic does not define one mandatory browser or native transport.
Those decisions must be evaluated as separate child issues with security, portability and maintainability in mind.
Done when
LibreSign can complete the external-signing lifecycle using at least one hardware-backed or local certificate implementation without exposing the private key to LibreSign and without adding device-specific logic to the PDF/PAdES layer.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Projects
- StatusShow more project fieldsNo status
Activity
[-][EPIC] Add local and hardware-backed certificate signing[/-][+]Add local and hardware-backed certificate signing[/+]