Struct BinaryIdentity 

pub struct BinaryIdentity {
    pub role: &'static str,
    pub name: String,
    pub path: String,
    pub sha256: Option<String>,
    pub running: bool,
    pub note: Option<&'static str>,
}

One executable dev-prune owns on this machine, and the digest a scanner sees.

A separate type from TrustRow because the hash has to survive into --json as a field of its own. Somebody comparing their copy against a published .sha256 should not have to parse it back out of a sentence.

Fields

role: &'static str

Stable identifier for --json: what this executable is for, not what it is named, so a reader does not have to know that devp is the short name.

name: String

The file name, for a human.

path: String

Where it is.

sha256: Option<String>

Lower-case hex SHA-256, or None when the file could not be read.

running: bool

Whether this is the executable answering right now.

note: Option<&'static str>

Why this one’s digest differs from the others, when it does.

Implementations

impl BinaryIdentity

pub fn scan_url(&self) -> Option<String>

The scan report for this file’s digest, if it could be hashed.