Skip to content

haskoki v0.3.0.0

Choose a tag to compare

@github-actions github-actions released this 09 Oct 17:34
· 92 commits to main since this release

Haskoki 0.3.0.0 - first public release (draft notes)

Draft for tag v0.3.0.0. Pre-publish: reading this file does
not mean the tag, the release, or the image exists yet.

Purpose

Haskoki is a Haskell PKCS#11 soft token (demonstrator) covering
APIs 2.40, 3.0, 3.1 and 3.2: real in-process crypto over
OpenSSL with honest refusals for the genuinely unsupported
calls. Not a certified HSM; no production-security claim.

Artifacts

Asset Contents
haskoki-0.3.0.0-linux-x86_64.tar.gz Bundle tree: libhaskoki.so, haskoki-ctl, bundled closure, licenses, smoke
haskoki-0.3.0.0.tar.gz Verified source distribution (unpacked + built + tested outside the checkout)
test-results-0.3.0.0.tar.gz Staged gate-evidence logs (Haskell suites, fast lane, demo-image runs)
release-manifest.json Source SHA, versions, build env, artifact hashes, tool pins
SHA256SUMS Checksums of the three archives and manifest
SHA256SUMS.asc Detached GPG signature of the checksum file
ghcr.io/mingulov/haskoki-demo:v0.3.0.0 Demo image (bundle + pinned proxy + external checker + entrypoint). Digest recorded in the release evidence; latest is a convenience pointer only, never the verified identifier.

Before publication, the owner must provide the public verification key
location and full fingerprint here; see the release checklist.
After importing that trusted key, verify gpg --verify SHA256SUMS.asc SHA256SUMS, then sha256sum -c SHA256SUMS (four OK results). Compare
the image repository digest with release-manifest.json.

Quick start

Prerequisites: Docker alone (the image pulls from GHCR on
first run; no checkout or local build needed). Then:

mkdir -p out
docker run --rm --network none --user "$(id -u):$(id -g)" -v "$PWD/out:/out" \
  ghcr.io/mingulov/haskoki-demo:v0.3.0.0 demo
# demo-ok: 8/8 verifications hold

To build and verify locally instead of pulling: from a
checkout of this tag, build the toolchain image per the
container Quick Start
(base image only), then run the release driver, which
stages the bundle, builds the demo image, and asserts
every lane:

HASKOKI_DEMO_TEST_OUT="$PWD/out/qualification" \
  HASKOKI_DEMO_REVISION="$(git rev-parse HEAD)" \
  sh scripts/test-demo-image.sh
# PASS: test-demo-image.sh (...); wall ~85 min

(Post-publish form shown; the image does not exist on GHCR
until the release is cut.)

Confirmed matrix

  • Hosts: Linux x86-64, glibc >= 2.43 (ubuntu:26.04 +
    libgmp10/libffi8/libnuma1 verified; the image carries
    its own userland).
  • Checker pkcs11-check 0.2.3 (PyPI pin), offline
    smoke/full profiles; proxy pkcs11-proxy-ng v0.2.2
    (TEST-ONLY loopback transport).
  • CI gates: static gates + cabal test all + bundle build +
    bare-install test + sdist out-of-checkout verify + fast
    lane + full demo-image lanes (demo, smoke, full direct,
    full proxy, compare).

Results (candidate CI at 0603322)

  • Checker smoke (743 collected tests, including skips and expected failures): zero findings, direct and proxied.
  • Checker full (10993 collected tests): direct 22 triaged findings
    (4 families); proxied 22 findings, all shared with direct,
    zero proxy-only.
  • Compare direct-vs-proxy: 83 frozen exclusions in 6 reasoned
    families + 22 shared findings (zero allowed variance).
  • Direct/proxy parity on the pinned proxy: 70 consumer legs
    hold; 19 quarantined legs in 5 quarantine entries with upstream
    causes.
  • Demo: 8/8 verifications hold. Proxy example: 5/5 steps hold.
  • Counts include skips and expected failures; findings are not silently
    treated as passing tests. Full tables and triage: release-results.

Limitations

  • Demonstrator scope: no certification; proxy example is
    TEST-ONLY transport (loopback, no auth/TLS).
  • 316 of 464 catalog mechanisms behavior-covered. Proxy v0.2.2
    resolved the previously recorded #35/#36/#37/#39 defects; the
    compared subset still has documented exclusions and skipped cases.
  • Vector corpora ship unfetched (separate opt-in recipe).
  • Full list: SUPPORTED-HOSTS;
    component licenses: dependency
    inventory
    .

Related tools

pkcs11-check
(external checker, same author),
pkcs11-proxy-ng
(proxy),
p11scope (call
observer; sample capture),
P11Lab (lab setup).

Development story

Read the development history and
Haskell design. The usage snapshot linked from
the history is cutoff-limited, not a final cost or personal-time claim.