Checksum in mise.lock also for asdf plugins

[danieleformichelli]

It would be useful to have a checksum also for asdf plugins to validate the version being installed is exactly the one we want.
Otherwise an attacker that gets control of the repo could republish a different malicious version with the same tag.

Example:
mise.toml

[tools]
swiftformat = "0.57.0"

[settings]
experimental = true
lockfile = true

mise.lock

[tools.swiftformat]
version = "0.57.0"
backend = "asdf:swiftformat"

[jdx]

asdf plugins don't support this. The bin/download script I'm not sure is standard enough for it to work with lockfiles very well. It's probably best to convert our plugins over to vfox which thankfully is something AI would likely be able to do pretty easily

[danieleformichelli]

Not sure how it asdf plugins work so it might be nonsense, but can't we use the git checksum of the tag?

[syhol]

Not a git checksum because although the asdf plugin itself is a git repo, the tool the plugin manages could be from anywhere: a git repo, an ftp server, a http server, an scp download, maybe just grabbing 10gb from /dev/urandom, who knows. The asdf plugin exposes the following shell scripts:

• bin/list-all
• bin/download
• bin/install
• (Plus some other optional executables)

We could tar c {download_dir} | md5sum the download directory after calling bin/download, but it could intentionally download different content each time. (e.g random uuids or datetimes), as jdx says: "I'm not sure is standard enough". asdf plugins weren't built to support it.

Whereas vfox plugins return the url + checksum, and lets mise perform the download.