Repository navigation
Releases
reallyme-ssi-v0.7.0
All workspace packages and internal dependency requirements advance together to
0.7.0.
- X.509 Name attributes retain their original ASN.1 class, tag number, and
constructed form. Text is validated against its declared string encoding;
callers constructingNameAttributevalues must supplyencoding. reallyme-trust-x509::projections::project_certificateprovides bounded,
DER-bound views of subject and issuer Names, separate SAN and IAN extensions,
and complete ordered CRL distribution points with extension criticality and
optional-field presence. Unsupported GeneralName structures retain their DER.- Projections borrow their source certificate; decoded BMP/Universal strings
use zeroizing owners and identifying values have redacted diagnostics. - Existing certificate-path, signature, revocation, timestamp, SKI, and mdoc
behavior remains available. Application-specific mdoc profiles stay outside
these generic certificate projections.
reallyme-ssi-v0.6.2
All workspace packages, internal dependency requirements, and the fuzz workspace
advance together to 0.6.2.
- Publish Data Integrity as
reallyme-data-integrityand presentation policy as
reallyme-vp-policy. Rust imports usereallyme_data_integrityand
reallyme_vp_policy; the composed SSI facade retains its existing module paths. - Release all 33 public component packages in dependency order. Every public
package must use thereallyme-namespace; release checks reject exceptions. - Public component archives include their documentation, licenses, and test
resources and are verified independently of the source checkout.
Existing protobuf field numbers and ProtoJSON field names are unchanged.
reallyme-ssi-v0.6.1
This patch adds explicit draft-07 Client Attestation PoP signing through
AttestationPopRequest::sign_for_draft07. The caller supplies the authenticated
client identifier for the iss claim; the existing sign method retains its
current claim set. Invalid and oversized identifiers return a typed error.
- The source-only EUDI registration crate adds an explicit TS5 v1.6 profile,
strict version-specific parsing, and lossless registration-document encoding.
Canonical profile material preserves fields used in service-definition binding.
Source consumers with exhaustiveProtocolProfilematches must handle
Ts5V1_6; the published crate API remains backward-compatible. - Rust CI requires every validation lane and checks the dedicated fuzz dependency
graph. Fuzz workflows build targets once before bounded execution. The bounded
test runner accepts Cargo binary and example identifiers without broadening
its filter syntax. - Conformance metadata distinguishes accepted evidence from coverage gaps and
keeps publication blockers explicit. reallyme-etsi-eaa-conformancejoins the public package set with its requirement
ledgers and dual-license files included. Cross-language contracts remain in
the canonical SSI protobuf package.
All workspace crates advance together to 0.6.1. Existing protobuf field numbers
and ProtoJSON field names are unchanged.
reallyme-ssi-v0.6.0
This release updates the OAuth and EUDI issuance boundaries and uses
ReallyMe COSE 0.2.10 to emit mdoc issuerAuth certificate chains in the
unprotected header required by ISO/IEC 18013-5.
- PAR requests expose managed OpenID4VCI and Request Object fields. Extensions
useAdditionalAuthorizationParameters::try_insertto reject duplicate
protocol-owned parameters. Rejected and temporary authorization values
are cleared from their owned allocations. - OAuth clients can validate attestation-challenge responses, classify bounded
DPoP nonce retries, and enforce an explicit authorization-response issuer policy
with stable typed failure reasons. - EUDI conformance uses structurally validated issuer-information summaries and
ordered credential-reuse policy options. Certificate authentication and
registered-attestation authorization remain the composing verifier's responsibility.
Rust consumers must update ParRequest construction and its extension map.
Source consumers of the private ETSI conformance crate must also update
IssuerMetadataFacts and ReusePolicy::ArfAnnexIi construction. Existing
protobuf field numbers and ProtoJSON field names are unchanged. All workspace
crates advance together to 0.6.0.
reallyme-ssi-v0.5.1
This patch accepts the 34-byte common-credential-root value encoding published
by reallyme-zk-api 0.2.0 in public SSI commitments. Precomputed issuance
signs the approved root and binds both its SHA-256 and Poseidon2 hash labels.
Generic SSI claim-opening verification still requires its own JCS transcript;
it does not reinterpret ZK openings as generic SSI openings.
All workspace crates advance together to 0.5.1.
reallyme-ssi-v0.5.0
This release gives ZK presentations a typed, protobuf-first shape: direct
credential, persona, and common-root presentations are separate variants.
Persona presentations identify private or public ownership, and common-root
proof packages keep credential status pointers inside the verified ZK data.
The released v1 credential wire fields retain their field numbers and
ProtoJSON shape; new persona and common-root profiles use distinct fields.
The Rust ZkPresentation struct becomes a tagged enum, so source consumers
must select a variant. SSI routes and evaluates presentation facts; the ZK
verifier remains responsible for authenticating proof packages, their profile,
issuer credentials, and status.
All workspace crates advance together to 0.5.0.
reallyme-ssi-v0.4.1
This release introduces reallyme-trust, a public certificate trust facade
over the released trust core, X.509, revocation, and protobuf packages.
- Certificate path decisions retain the selected leaf-to-anchor SHA-256 path,
selected anchor, policy, evaluation time, status evidence, and fixed failure
reasons. - An explicit portable signature backend verifies supported certificate
signatures and fails closed when an algorithm, path constraint, or required
status capability is unavailable. - An opt-in OpenSSL backend retains native strict path validation and broader
certificate-signature algorithm support for existing consumers. - The facade's publication graph uses registry-sourced trust core and X.509
packages, with a single X.509 certificate type for callers and backends. - Decision evidence redacts linkable identifiers from debug output and clears
them on drop.
reallyme-ssi-v0.4.0
This release raises the minimum supported Rust version to 1.99, updates the
pinned Crypto, Codec, COSE, and JOSE dependencies, and changes the public
credential proof-binding API.
- Credential proof bindings now include the transaction-data hash in the
session commitment and an issuer signature over the credential validity
interval and status pointer.CredentialProofBindinggains a required field,
andcredential_bindinggains a required argument. - SD-JWT disclosure selection gains an exact-scope API that rejects selected
parent disclosures containing cleartext claims outside the requested paths. - WRPRC authentication retains the presented signer certificate chain and
exposes authenticated registration scope, canonical registry and status
URIs, and registrar-provided descriptions for trust and consent evaluation. - Status-list verification exposes authenticity and freshness checks without
selecting a private status index. reallyme-mdocdeclares thereallyme-codec/base64urlfeature used by its
data-element projection, so the published crate compiles in isolation.
reallyme-ssi-v0.3.4
This patch release aligns DPoP HTTP target URI validation with RFC 9449 by
ignoring query and fragment components during htu comparison without
weakening the surrounding HTTPS URL policy.
DPoP target URI normalization
normalize_uri_without_query_or_fragmentnow parses the bounded target as a
URL, removes its query and fragment, and then applies the remaining HTTPS,
authority, userinfo, and host checks.- Raw backslashes remain rejected before WHATWG URL parsing so an ambiguous
authority or path cannot be reinterpreted during normalization. - Signed-proof coverage demonstrates query-only, fragment-only, and combined
normalization, with negative controls for scheme, host, path, userinfo,
backslashes, malformed URLs, replay,ath, andcnf.jktbinding. - All workspace crates, including source-only internal crates, advance in
lockstep to version 0.3.4.
reallyme-ssi-v0.3.3
This patch release adds certificate-path verification for IETF Token Status
List JWTs without changing the existing raw-key verifier.
Token Status List certificate authentication
verify_token_status_list_jwt_with_x5cparses a bounded, leaf-firstx5c
protected header and passes the exact DER chain plus verification time to a
caller-supplied X.509 path resolver.- The new verifier accepts only
alg = ES256,typ = statuslist+jwt, and
x5cin the protected header. It rejects duplicate members, alternate key
selectors, empty or malformedx5cencodings, and per-certificate,
path-count, aggregate-path, and compact-JWT limit violations before trust
resolution. The caller's resolver remains responsible for DER certificate
and path validation. - Resolver-authenticated leaf keys are validated and canonicalized through a
P-256 JWK before JWS verification. The existing subject, decompression,
status-value, index,iat,exp,ttl, and local freshness checks remain in
force. verify_token_status_list_jwtretains its original raw-key contract and
continues to reject embeddedjwkandx5ckey material.- All workspace crates, including source-only internal crates, advance in
lockstep to version 0.3.3.