Skip to content

Better code authentication on crates.io #18

Open

Description

@Shnatsel

crates.io currently lacks a number of fairly basic security features, such as requiring signatures from several maintainers to issue a package release.

Designing a solution for this from scratch or gradually patching for more and more stuff sound like dubious undertakings. Fortunately, The Update Framework provides a fairly comprehensive solution that is not overly tedious for crate maintainers. A Rust implementation is in progress.

Discussion on crates.io issue tracker: rust-lang/crates.io#75

Activity

  1. changed the title [-]Better code authentication[/-] [+]Better code authentication on crates.io[/+] on Jan 8, 2019
  2. tarcieri commented on Jan 8, 2019

    @tarcieri
    Member

    Here's a proposal I wrote to use TUF for crates.io signing withoutboats/rfcs#7

  3. heavypackets commented on Jul 12, 2019

    @heavypackets

    I've yet to get through all of the prior work done so far in detail, but this will be a high priority through the rest of the year for me. I will say, there are a lot parallels here to Notary which I now help maintain. Notary uses TUF metadata in a way similar to what has been proposed, so there is some prior art to reference to also help ramp his effort back up. Are there any current items in progress?

  4. tarcieri commented on Jul 12, 2019

    @tarcieri
    Member

    @heavypackets my linked proposal in the previous post is the last I know of to integrate TUF into crates.io.

    It’s something I’ve been meaning to work on when I have some spare cycles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions