A Go library for working with ETSI trust lists — both the traditional XML-based Trust Status Lists (ETSI TS 119 612) and the modern JSON-based Lists of Trusted Entities (ETSI TS 119 602, LoTE). The library was created to cater to the evolving EUDI wallet ecosystem but other uses are possible. Feel free to drop a PR or an issue if you see something you would like to change.
The library is fully reentrant. There is no caching of URLs or other artefacts so make sure you fetch your TSLs/LoTEs from a CDN or similar and ensure availability.
- Full TSL parsing: Parse, validate, and process Trust Status Lists
- XML Digital Signature Validation: Built-in validation of XML signatures on TSLs
- Certificate Pool Creation: Build
x509.CertPoolfrom TSLs for certificate verification - Extensible Crypto Support: Brainpool curves and other non-standard algorithms via
go-cryptoutil - XSLT Transformation: Transform TSLs to HTML with embedded stylesheets
- LoTE parsing and generation: Create, load, validate, and publish LoTE JSON documents
- TSL → LoTE conversion: Convert existing ETSI TS 119 612 TSLs to LoTE format
- JWS signing and verification: Sign LoTEs with JWS (file-based keys or PKCS#11/HSM)
- Content validation: Structural validation of LoTE documents before publishing
- Multiple digital identity types: X.509 certificates, JWK keys, and DIDs
- Merge and sequence management: Merge multiple LoTEs and auto-increment sequence numbers
- Pipeline Processing: YAML-configurable pipeline for batch TSL and LoTE processing
- Structured Logging: Configurable logging with multiple output formats
go get github.com/sirosfoundation/g119612The example below assumes you have imported the crypto/x509 and etsi119612 module (the latter from this package).
First step: fetch and create a TSL object
import (
"github.com/sirosfoundation/g119612/pkg/etsi119612"
)
tsl, err := etsi119612.FetchTSL("https://example.com/some-tsl.xml")
if err != nil {
// do some error handling
}Next step: build a cert-pool from the trust status list with default validation policy
pool := tsl.ToCertPool(etsi119612.PolicyAll)Finally: validate some cert
_, err = cert.Verify(x509.VerifyOptions{Roots: pool})
if err != nil {
//cert is INVALID
}Load a LoTE from a URL or file:
lote, err := etsi119602.FetchLoTE("https://example.com/lote.json", nil)
if err != nil {
// handle error
}
fmt.Printf("Territory: %s, Entities: %d\n",
lote.SchemeInformation.Territory,
len(lote.TrustedEntities))Validate a LoTE before publishing:
if err := lote.Validate(); err != nil {
// LoTE has structural issues
}Convert an existing TSL to LoTE format:
tsl, _ := etsi119612.FetchTSL("https://example.com/tsl.xml")
lote := etsi119602.FromTSL(tsl)The tsl-tool command provides batch processing of TSLs using a YAML-defined pipeline:
# Build the tool
make build
# Run with a pipeline configuration
./tsl-tool --log-level debug pipeline.yamlCreate a YAML file defining your processing steps:
# pipeline.yaml
- set-fetch-options:
- user-agent:TSL-Tool/1.0
- timeout:60s
- load:
- https://ec.europa.eu/tools/lotl/eu-lotl.xml
- select:
- reference-depth:2
- transform:
- embedded:tsl-to-html.xslt
- /var/www/html/tsl
- html
- generate_index:
- /var/www/html/tsl
- "EU Trust Lists"
# generates both index.html and report.html
# add 'no-report' to skip report generationThe tsl-tool CLI automatically registers brainpool curve support via
go-cryptoutil, enabling parsing and signature verification for EU TSLs
that use brainpool P256r1/P384r1/P512r1 certificates (e.g. Germany's gematik).
When using the library programmatically, set CryptoExt on the pipeline context:
import (
"github.com/sirosfoundation/go-cryptoutil"
"github.com/sirosfoundation/go-cryptoutil/brainpool"
"github.com/sirosfoundation/g119612/pkg/pipeline"
)
ext := cryptoutil.New()
brainpool.Register(ext)
ctx := &pipeline.Context{}
ctx.CryptoExt = ext
// CryptoExt automatically propagates to TSL fetch options and certificate pool building| Step | Description |
|---|---|
load |
Load TSL from URL or file path |
select |
Build certificate pool from loaded TSLs |
transform |
Apply XSLT transformation to generate HTML |
publish |
Write TSLs to output files |
generate |
Generate new TSL from metadata |
generate_index |
Create HTML index page + pipeline report |
report |
Generate standalone pipeline report |
log |
Output messages to the log |
set-fetch-options |
Configure HTTP client options |
echo |
No-op placeholder step |
| Step | Description |
|---|---|
load-lote |
Load LoTE from URL or file path, optionally verify JWS signature |
generate-lote |
Generate LoTE from a directory structure (YAML metadata + cert/JWK/DID files) |
publish-lote |
Write LoTE JSON files, optionally sign with JWS (file key or PKCS#11/HSM) |
convert-to-lote |
Convert all TSLs on the context stack to LoTE format |
merge-lote |
Merge multiple LoTEs into a single LoTE |
increment-lote-sequence |
Increment the sequence number on all LoTEs in context |
Convert an EU TSL to LoTE and publish as signed JSON:
- set-fetch-options:
- user-agent:TSL-Tool/1.0
- timeout:60s
- load:
- https://ec.europa.eu/tools/lotl/eu-lotl.xml
- select:
- reference-depth:2
- convert-to-lote:
- merge-lote:
- increment-lote-sequence:
- publish-lote:
- /var/www/html/lote
- /path/to/signing-cert.pem
- /path/to/signing-key.pemGenerate a LoTE from a directory structure:
- generate-lote:
- /path/to/lote-source
- publish-lote:
- /var/www/html/loteThe generate-lote step expects a directory with YAML metadata and identity files:
lote-source/
├── scheme.yaml
└── entities/
├── my-issuer/
│ ├── entity.yaml
│ ├── signing-cert.pem # X.509 certificate (PEM or DER)
│ └── auth-key.jwk # JWK key (JSON)
└── my-verifier/
├── entity.yaml
└── identity.did # DID identifier
scheme.yaml:
operatorNames:
- language: en
value: "My Trust Scheme Operator"
schemeName:
- language: en
value: "My Trust Scheme"
schemeType: "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/EUgeneric"
territory: "SE"
sequenceNumber: 1entity.yaml:
entityId: "https://issuer.example.com"
names:
- language: en
value: "Example Credential Issuer"
status: "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted"
services:
- serviceType: "http://uri.etsi.org/TrstSvc/Svctype/CA/QC"
serviceNames:
- language: en
value: "Qualified Certificate Service"
status: "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted"| Package | Description |
|---|---|
etsi119612 |
Core TSL types, parsing, and certificate pool creation (ETSI TS 119 612) |
etsi119602 |
LoTE types, parsing, validation, fetching, and TSL→LoTE conversion (ETSI TS 119 602) |
dsig |
XML Digital Signature validation (including PKCS#11/HSM support) |
jws |
JWS signing and verification for LoTE documents (file keys and PKCS#11/HSM) |
pipeline |
YAML-configurable pipeline processing for both TSL and LoTE workflows |
validation |
URL, file path, and output directory validation utilities |
xslt |
XSLT transformation with embedded stylesheets |
logging |
Structured logging framework |
utils |
Common utility functions |
Document for the reference: https://github.com/EWC-consortium/eudi-wallet-rfcs/blob/main/ewc-rfc012-trust-mechanism.md#433-relying-parties
flowchart TD
Issuer["Issuer"] -- Issues Credential --> Credential["Verifiable Credential"]
Credential -- Stored in --> Wallet["Wallet Unit"]
Wallet -- Presents Credential --> Verifier["Relying Party / Verifier"]
Credential -- Includes --> Key["Public Key / Certificate"]
Key -- Anchored in --> TL["Trusted List (EWC TL)"]
Verifier -- Verifies Issuer & Credential --> TL
Wallet -- Verifies Issuer & Credential --> TL
Wallet -- Verifies Verifier --> TL
Verifier -- Verifies Wallet Unit Attestation --> TL
TL -. Must Register .-> Issuer & WalletProvider["Wallet Provider"]
TL -. "Recommended to be Registered - Section 4.3.2.2" .-> Verifier
Issuer:::actor
Credential:::doc
Wallet:::actor
Verifier:::actor
Key:::key
TL:::trustlist
classDef trustlist fill:#fdf6b2,stroke:#d97706,color:#92400e
classDef actor fill:#f0f9ff,stroke:#0284c7,color:#0c4a6e
classDef doc fill:#f3f4f6,stroke:#6b7280,color:#374151
classDef key fill:#ecfccb,stroke:#65a30d,color:#365314
linkStyle 1 stroke:#000000
Contributions are welcome! Please feel free to submit issues or pull requests.
- Go 1.25 or later
- Make
make testIf you want to "make gen" to re-generate the golang from the etsi XSD then you must install https://github.com/xuri/xgen first. Note that the generated code is post-processed (sed) to fix a couple of "features" in xgen that I am too lazy to pursue as bugs in xgen at this point. This stuff may change so run "make gen" at your own peril. The generated code that is known to work is commited into the repo for this reason - ymmw.
BSD 2-Clause License - see LICENSE.txt