Futureweb

Privacy

A Deputy vault is a hash check

An October 24 note says to vault crates an agent adds and check them against Cargo.lock and RustSec. A matching hash is not a promise that crates.io was honest.

The short version

The note says to vault the lockfile, verify hashes against Cargo.lock, and scan RustSec, including when crates.io is unavailable. Cargo's own lockfile manual is the format. RustSec is the advisory database the note names.

A lockfile pin, dated October 24

Remade with Rust's October 24 note on Deputy says to vault every crate an agent adds, verify hashes, and keep a build working when crates.io blips. The body of the note says Deputy vaults dependencies, checks SHA-256 hashes against Cargo.lock, scans RustSec, and still builds offline. It says an agent will add a niche crate for a problem the standard library could have handled, and that the pin has to be in place before that add. This page does not reprint the command lines.The key stays with the holder.

What Cargo already writes down

Cargo's own guide distinguishes the manifest, which a person edits, from the lockfile, which records the resolved graph. A hash check against that lockfile is a check that a stored crate still matches the resolution Cargo wrote. It is not a new kind of trust. If the lockfile was produced by resolving a malicious version, the hash will match the malicious version. The Deputy note is a vault and a gate around that file. Rust's documentation is the description of the file itself.A session is not a lockfile.

What RustSec is

RustSec publishes advisories for Rust crates. The note says Deputy scans it. A scan can tell you that a version has a published advisory. It cannot tell you that a crate nobody has reviewed is fine. The October 24 note's phrase "advisory gate before promote" is only as wide as the database on the day of the scan. That limit is why a vault is not a substitute for reading what the agent added. The document named in the sources is the record this page will keep.Gmail's ads line is a different privacy change.

Who the vault is for

The person in scope is a developer whose agent is growing a lockfile. A team that already vendors crates and reads RustSec by some other tool is not uncovered because it skipped this pin. The note's offline claim matters when crates.io is down or when a build should not phone out. It does not move the copyright or the license of the crates. Those stay with the crates. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.What a TLS certificate binds.

A hash is the mechanism

The mechanism the note offers is the hash match plus the advisory scan, before a binary is promoted. That is why this brief exists. A second link to the house site is unnecessary once the note is a source. The other two documents are Cargo's lockfile guide and RustSec's database, which are the objects the note says it checks. Asked directly, Does the note stop an agent from adding a crate? It says the pin has to be loaded before the first add, and that a vault should gate promotion. An agent can still propose a dependency. The gate is the note's claim about what happens after.

What the note will not catch

A crate with no advisory, a hash that matches a bad resolution, and a transitive dependency the reader did not look at can all pass a green gate. The note is right that an unaudited tree can become the product. The gate reduces one class of surprise. It does not review behavior. Asked directly, Is RustSec a complete list of malicious crates? No. RustSec is an advisory database. An empty scan means no matching advisory, not that a new crate is safe. The document named in the sources is the record this page will keep.

What this page will not promise

It will not promise that a vaulted build is free of malware, or that crates.io was wrong on a given day. The record is a dated note that names Cargo.lock and RustSec, plus those two public documents, plus the limit of a hash. Asked directly, Does Cargo already record dependency checksums? Cargo's lockfile is the project's record of which versions were resolved. The Deputy note says to verify a vault against that file. It does not replace Cargo. The document named in the sources is the record this page will keep.The advisory is still the advisory.

The open item

The open item is whether a particular agent session added a crate the standard library already covered. That can be answered only by reading the lockfile diff. The note tells you to vault the diff. It does not read it for you. Asked directly, What does the October 24 Deputy note say it checks? Hashes against Cargo.lock, a vault of the dependencies, and a RustSec scan. The note also says builds should keep working when crates.io is unreachable. The document named in the sources is the record this page will keep.

A statute is a different privacy story

Pennsylvania's advertising statute, filed separately, is a law about synthetic ads. Deputy is a dependency pin. One does not enforce the other. The short answer this page will stand on is this: The note says to vault the lockfile, verify hashes against Cargo.lock, and scan RustSec, including when crates.io is unavailable. Cargo's own lockfile manual is the format. RustSec is the advisory database the note names. Asked directly, Are the install steps in this brief? No. They stay on the October 24 note. This page keeps the check the note says matters.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Remade Deputy note
  2. Cargo lockfile
  3. RustSec

Questions

What does the October 24 Deputy note say it checks?

Hashes against Cargo.lock, a vault of the dependencies, and a RustSec scan. The note also says builds should keep working when crates.io is unreachable.

Does Cargo already record dependency checksums?

Cargo's lockfile is the project's record of which versions were resolved. The Deputy note says to verify a vault against that file. It does not replace Cargo.

Is RustSec a complete list of malicious crates?

No. RustSec is an advisory database. An empty scan means no matching advisory, not that a new crate is safe.

Does the note stop an agent from adding a crate?

It says the pin has to be loaded before the first add, and that a vault should gate promotion. An agent can still propose a dependency. The gate is the note's claim about what happens after.

Are the install steps in this brief?

No. They stay on the October 24 note. This page keeps the check the note says matters.