resources
1 row where summary = "research/papers/why-x509-certs-should-be-secondary-evidence" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: last_checked (date)
type 1
level 1
access 1
year 0
| id | type | name | url | maintainer | status | last_checked | date ▲ | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| kerione-why-x509-certs-should-be-secondary-evidence | Papers and paper collections paper | Why X509 Certs Should Be Secondary Evidence of Org Identity | https://dhh1128.github.io/papers/x509-prob.html | Daniel Hardman | changed within the last six months, or a live service active | 2026-10-14 | practitioner | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | A position paper by Daniel Hardman arguing that X.509 certificates should be secondary, not primary, evidence of an organization's identity, with ACDCs (Authentic Chained Data Containers) such as vLEIs carrying the primary weight. It works through mismatched lifespans, opaque governance, the post-quantum path, single-key signing, missing pre-rotation, unsequenced signatures, maintenance, revocation and scale. For practitioners choosing evidence for organizational identity. | Daniel Hardman | 1.4 (item CC-POS-241104) | keri.one KERI Resources page keri-one-resources | Why X509 Certs Should Be Secondary Evidence of Org Identity research/papers/why-x509-certs-should-be-secondary-evidence | 1 | 1 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE resources (id TEXT PRIMARY KEY, type TEXT REFERENCES types(id), name TEXT, url TEXT, maintainer TEXT,
status TEXT REFERENCES statuses(id), last_checked TEXT, date TEXT, year INTEGER, level TEXT REFERENCES levels(id),
evidence TEXT REFERENCES evidence(id), access TEXT REFERENCES access(id), abstract TEXT, authors TEXT, series TEXT,
chair TEXT, minutes TEXT, recording TEXT, media TEXT, decisions TEXT, version TEXT, language TEXT, license TEXT,
release TEXT, pushed TEXT, depends TEXT, since TEXT, via TEXT REFERENCES resources(id),
summary TEXT REFERENCES notes(path), note TEXT, has_abstract INTEGER, has_summary INTEGER,
kind TEXT REFERENCES kinds(id), sector TEXT REFERENCES sectors(id), country TEXT, products TEXT);