Struct SignedRequest 

pub struct SignedRequest<'a> {
    pub body_sha256: &'a str,
    pub signature_base: &'a str,
    pub signature: &'a str,
    pub body: Option<&'a str>,
}

The signed-request material a device-authenticated leaf carries in its request field: enough for an offline verifier to check the signature against nothing but the device’s key, itself carried by an earlier approve or enroll leaf (see docs/design/part5-plan.md’s “Verifying offline”).

What a signature proves is that the device sent a request with this method, path, query and body digest — not what the server made of it. The path and query bind a pull’s project and a revoke’s id; body binds the rest of a device-management action, whose small body is kept whole. A push’s or a delete’s body is the file, or names it, and is not kept, so for those the signature vouches for the request and its digest, and subject is the server’s word.

Fields

body_sha256: &'a str

Content-Digest’s sha-256 value, base64 standard: the hash of the request body — for a push, the JSON that carried the file, not the file.

signature_base: &'a str

The exact bytes RFC 9421 §2.5 built and the device signed.

signature: &'a str

The signature itself, base64 standard.

body: Option<&'a str>

The request body itself, for the actions whose body is a few bytes of JSON with no secret in it: approve, deny, revoke, authkey_create and authkey_revoke. None, written null, for a push, a delete, a pull and the job actions.