Download the PHP package komma-softhouse/asice-engine without Composer
On this page you can find all versions of the php package komma-softhouse/asice-engine. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download komma-softhouse/asice-engine
More information about komma-softhouse/asice-engine
Files in komma-softhouse/asice-engine
Package asice-engine
Short Description ASiC-E containers with XAdES signatures for Estonian eID: ID-kaart, Smart-ID and Mobile-ID. Hash in, container out | Komma SoftHouse
License proprietary
Homepage https://github.com/komma-softhouse/asice-engine
Informations about the package asice-engine
ASiC-E engine
ASiC-E containers with XAdES signatures for Estonian eID. Hash in, container out: the engine builds the container and the signature document, hands you the digest to sign, and finishes the job when the value comes back — from an ID-kaart through Web eID, from Smart-ID or from Mobile-ID. It then fetches the OCSP answer and the time-stamp that make the signature long-term.
Used by komma-softhouse/filament-eesti-billing; usable on its own in any PHP application.
Requirements
PHP 8.3+, ext-openssl, ext-zip, ext-dom. No other dependency.
Installation
Signing
Then, once the signature value is back:
The signature value is verified against the hash before anything is written: a wrong value never lands in the container. A revoked certificate stops the process.
Validating
Validation recomputes every file digest against its Reference, so a file changed after signing is reported by name.
Services
By default the engine asks the OCSP responder named in the signer's certificate (SK's public AIA responder for Estonian eID) and http://tsa.sk.ee for the time-stamp. Point them elsewhere, or hand the issuer certificate over when you already have the chain:
If either service cannot be reached, the container is still written with a valid basic signature and notes explains what is missing.
Several signers
createSignature() can run again on a saved container; each finished signature becomes its own META-INF/signatures{n}.xml. The data files are untouched.
What is in the container
mimetype (stored, first), META-INF/manifest.xml, the data files, and one META-INF/signatures{n}.xml per signature holding the XAdES structure: a Reference per file, the signed properties with the signing time and the certificate digest, the signature value, and the unsigned properties with the time-stamp and the OCSP answer.
Testing
The suite signs with a throwaway key pair, so it runs offline; only the time-stamp and OCSP steps need a network, and their absence is a note, not a failure.
Security
If you discover a security issue, email [email protected] instead of using the issue tracker.
License
Commercial. See LICENSE.md.
All versions of asice-engine with dependencies
ext-dom Version *
ext-openssl Version *
ext-zip Version *