Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trust crates published by dtolnay, epage, cuviper, Amanieu #6697

Merged
merged 1 commit into from
Jul 7, 2023

Conversation

jameysharp
Copy link
Contributor

We discussed this in today's Wasmtime meeting and the consensus was that we trust each of these people to have a sufficient standard of care for anything they release.

This reduces our estimated audit backlog by about 184 kLOC.

For the most part, the trust records I'm adding here are identical to trust records that Mozilla is using. The fact that they've also decided these publishers are trustworthy is reassuring additional evidence for our decision. The exceptions and notable cases are as follows:

I've chosen to not trust three crates by these authors that Mozilla did not trust. I suspect Mozilla simply doesn't use these crates or has manually audited them, rather than there being any problem with the crates themselves. But I've chosen to be conservative about what we trust.

  • autocfg: we only have an exception for an old version, and that version is only used transitively by wasi-crypto.
  • env_logger: Mozilla has audited some versions; we should update, or add delta audits.
  • thread_local: only used by tracing-subscriber which is only used in dev-dependencies.

I've trusted one crate that Mozilla did not: libm, when published by Amanieu. We're trusting libc when published by the same author, and libm is a small extension of the same trust.

Recent versions of the toml crate have been published by epage so I looked at in this process, but Mozilla only trusts the older versions which were published by alexcrichton. They've been delta-auditing the newer versions. I've chosen to follow their lead on this; Alex is a trusted contributor to Wasmtime anyway.

This PR is a step toward #6672, but I've run cargo vet myself rather than relying on anyone else's vetting.

@jameysharp jameysharp requested a review from a team as a code owner July 6, 2023 17:47
@jameysharp jameysharp requested review from cfallin and removed request for a team July 6, 2023 17:47
@jameysharp jameysharp enabled auto-merge July 6, 2023 17:53
@jameysharp jameysharp disabled auto-merge July 6, 2023 17:57
@jameysharp
Copy link
Contributor Author

Oops, I typo'd David Tolnay's username so he's not actually in this PR. I want to clean that up before merging.

We discussed this in today's Wasmtime meeting and the consensus was that
we trust each of these people to have a sufficient standard of care for
anything they release.

This reduces our estimated audit backlog by about 184 kLOC.

For the most part, the trust records I'm adding here are identical to
trust records that Mozilla is using. The fact that they've also decided
these publishers are trustworthy is reassuring additional evidence for
our decision. The exceptions and notable cases are as follows:

I've chosen to not trust three crates by these authors that Mozilla did
not trust. I suspect Mozilla simply doesn't use these crates or has
manually audited them, rather than there being any problem with the
crates themselves. But I've chosen to be conservative about what we
trust.

- autocfg: we only have an exception for an old version, and that
  version is only used transitively by wasi-crypto.
- env_logger: Mozilla has audited some versions; we should update, or
  add delta audits.
- thread_local: only used by tracing-subscriber which is only used in
  dev-dependencies.

I've trusted one crate that Mozilla did not: libm, when published by
Amanieu. We're trusting libc when published by the same author, and libm
is a small extension of the same trust.

Recent versions of the toml crate have been published by epage so I
looked at in this process, but Mozilla only trusts the older versions
which were published by alexcrichton. They've been delta-auditing the
newer versions. I've chosen to follow their lead on this; Alex is a
trusted contributor to Wasmtime anyway.
@jameysharp jameysharp changed the title Trust crates published by dtolney, epage, cuviper, Amanieu Trust crates published by dtolnay, epage, cuviper, Amanieu Jul 6, 2023
@jameysharp
Copy link
Contributor Author

Now that I've correctly added dtolnay to this PR, I'd appreciate re-review before we merge this.

@alexcrichton alexcrichton added this pull request to the merge queue Jul 7, 2023
Merged via the queue into bytecodealliance:main with commit 7a858de Jul 7, 2023
19 checks passed
@jameysharp jameysharp deleted the vet-trust branch July 7, 2023 16:45
@jameysharp jameysharp mentioned this pull request Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants