To me, the two major problems are:

  1. no namespaces

Someone uploads “serde2”? that’s blocked forever. Someone uploads a typo version of a popular package? Too bad for you, learn how to type.

  1. the github connection

If you want to contribute to crates.io you’re bound to github. No gitlab, codeberg, gitee, sourcehut, etc.

Not sure if there are any other problems, but those two seem like the biggest things and #1 is AFAIK not something they ever want to change + it would be difficult to as one would need a migration strategy.

  • Turun@feddit.de
    0·
    1 year ago

    I know a lot of people want namespaces. And I think it would be nice for a bigger project to have an obvious way to show which packages are part of this big project, and which are not. For example the different serde serialization formats would not need to be listed in the docs, but simply be present in one single serde-formats namespaces.

    It it does fuck all for type squatting. Sure, now I’m safe from getting malicious code by doing tokio/tokiu-http, but tokiu/tokio-http can still be malicious!

    The only solution to type squatting would be a checksum. So instead of adding Tokio to your toml file you’d have to add e.g. tokio-fld, with the fld part being some kind of check that is derived from the name. Similar to a hash, all names that are similar to tokio would get a wildly different suffix.

    • sugar_in_your_tea@sh.itjust.works
      0·
      1 year ago

      I think you could get it with a signature, just like with Linux repos. Basically, the org would sign the metadata so you know it came from that org’s key.

      That way you’d need both a malicious name and access to the key. You don’t need the suffix here, just a section in the toml that lets you list keys per org, and if it changes, you’d get prompted to update it.

      • Turun@feddit.de
        0·
        1 year ago

        I don’t think changing is the problem, incorrect initial entry is the problem. Linux has centralized package maintainers, cargo does not (or am I wrong?)

        Or do you mean that adding a namespace would require a key and then all crates in that namespace are unlocked? Then only the initial cargo add would be dangerous, all subsequent ones in the same namespace would not require manual confirmation.

        • sugar_in_your_tea@sh.itjust.works
          1·
          1 year ago

          Yes, I’m saying that adding a namespace would require a key, and all releases would be signed with that key. That works similarly to installing a separate repo in a Linux distro, you’d import the key and mark it as trusted, and then signatures would be verified for each download.

          So yes, only the initial cargo add would be “dangerous,” and there would be a prompt for the user to verify that they have the right key (which they could verify on the project homepage).