Skip to content

Use hash of certificate for user and member IDs#2279

Merged
achamayou merged 46 commits into
microsoft:mainfrom
jumaffre:member_id_hash_cert
Mar 10, 2021
Merged

Use hash of certificate for user and member IDs#2279
achamayou merged 46 commits into
microsoft:mainfrom
jumaffre:member_id_hash_cert

Conversation

@jumaffre
Copy link
Copy Markdown
Contributor

@jumaffre jumaffre commented Mar 8, 2021

Fixes #1378 (part II)

We now use a hex-encoded string of the SHA-256 hash of the DER-encoded certificate (a.k.a fingerprint) for the member and user IDs.

This has the following implication: the user and member certs and digests KV tables are gone and the keyId in signed HTTP requests is set to the Member/User ID.

The Python infra still tracks members/users as 0, 1, etc. (local_id) but also knows their CCF IDs (service_id).

@jumaffre jumaffre requested a review from a team as a code owner March 8, 2021 15:20
@ghost
Copy link
Copy Markdown

ghost commented Mar 8, 2021

member_id_hash_cert@20196 aka 20210310.28 vs main ewma over 20 builds from 19816 to 20184
images

Comment thread src/node/client_signatures.h
Comment thread doc/schemas/gov_openapi.json
Comment thread src/node/certs.h
Comment thread src/node/entity_id.h Outdated
Comment thread src/node/node_id.h Outdated
Comment thread src/node/rpc/member_frontend.h Outdated
Comment thread tests/e2e_logging.py Outdated
Comment thread tests/start_network.py Outdated
Comment thread CHANGELOG.md Outdated
Comment thread src/node/entity_id.h Outdated
Comment thread CHANGELOG.md Outdated
Comment thread doc/governance/adding_member.rst Outdated
Comment thread src/node/entity_id.h Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Re-evaluate the use of KV-driven incrementing IDs for users, members, nodes and proposals

3 participants