I remember a story where people asked about blobs included in Ventoy and there were no comments from the devs, leading to suspicion.
At the time it wasn’t clear to me if there was any substance to the story or if it was the usual Internet exaggeration, so I resolved to ignore it for the time being and saved a reminder to look into it after a while.
Now my reminder fired off and I looked around, but couldn’t find how the story ended… do you know?
It didn’t end. Fuck Ventoy, I’ll use something else
GLIM is an option that is a little harder to use but has the ability to load up multiple ISO’s, and it is fully open source.
Blobs aren’t really a concern as they reference the sources which produce the same binaries, but there are suspicions of compromise due to the Lemmy comments mentioned in the thread. The official accounts’ comments alleviate some of that, though.
Looks like contributor is busy with work. Always the risk with open source. If things aren’t raised in a reasonable manner, I can imagine the temptation is to follow it up with a middle finger.
Many seemed to care about it enough to bash it, but not enough to create and maintain a fork. They just want to boss it over the maintainer.
I’m in a similar boat to you; whether the blobs constitute a security threat seems to still be up in the air. I read through the issue thread on github a few months back and it seemed the vast majority of the blobs were built by scripts contained in the repository, but some weren’t documented well, leading to uncertainty.
The comment by Long0x0 on Aug 05 lists a lot of the blob files.
Not fixed yet. People either quit, let their threat model allow Ventoy’s shellscripts to git-commit bins, or built it from source (i.e. PKGBUILD or ebuild).
