Expand description
The biometric proxy’s shapes: one device’s enrolment, the purposes it carries, and the blob a release hands back.
No wrapped blob rides the enrolment list. A view draws which purposes a device enrolled and when each was last released; the bytes stay behind the release command, which answers the client that unwraps them. The list is read by every client of the server, so a blob there would be every device’s ciphertext handed to every viewer for nothing.
A purpose is the consumer’s own name ("vault" in v1) and is opaque to the
core: the blob’s shape is the consumer’s business, and a second consumer is
a second purpose string rather than a change to any of these types.
Re-exports§
use std::time::SystemTime;🔒use serde::Deserialize;🔒use serde::Deserialize;🔒use serde::Serialize;🔒use serde::Serialize;🔒use uuid::Uuid;🔒
Structs§
- Biometric
Blob - The blob a release answers with: exactly the bytes the client enrolled, base64 on the wire and opaque to the core.
- Biometric
Enrolment - One device’s enrolment: the id its client minted, the device’s own name, and the purposes it registered.
- Biometric
Purpose - One purpose’s enrolment as a view draws it: the consumer’s own name and when it was enrolled and last released.