Extended Cryptographic Canaries #10
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: phryk-evil-mad-sciences-llc/xmpp-service#10
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We want granular cryptographic assurances, with layered signatures
so one person can issue an assurance and others can publicly verify
its veracity.
A good bit of time was already wasted on this in deadhand as GnuPG is awful.
Wait for sequoia-sop python bindings to be completed, fix up deadhand and
implement a script for sending assurances and their verifications as well as
integrating display of those into xmpp-site.
We will want separate canaries to assure:
We will also need (internal?) policies or guidelines on what to do
when an expected assurance or verification isn't coming in.