this post was submitted on 19 May 2025
573 points (98.8% liked)

linuxmemes

25051 readers
1490 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] slazer2au@lemmy.world 77 points 5 days ago (4 children)
    [–] rtxn@lemmy.world 122 points 5 days ago (4 children)
    [–] axEl7fB5@lemmy.cafe 1 points 21 hours ago

    i been waiting for this so long

    [–] possiblylinux127@lemmy.zip 21 points 4 days ago (1 children)

    There is also a new community fork to get rid of the blobs and bad cert loading. The ventroy dev has made a bunch of concerning choices so some people hard forked the code. I forgot where is was though.

    [–] pogmommy@lemmy.ml 18 points 4 days ago (1 children)
    [–] possiblylinux127@lemmy.zip 7 points 4 days ago

    That's the one

    [–] troed@fedia.io 42 points 5 days ago (1 children)

    oh wow that really put the trust back into Ventoy. Nice! Thanks for the link

    [–] fmstrat@lemmy.nowsci.com 16 points 4 days ago

    Happened after a partner product in the Ventoy repo was found to have a pretty major vulnerability due to a... you guessed it, pre-compiled supply chain attack.

    [–] Turret3857@infosec.pub 2 points 4 days ago (1 children)

    Took them over a year to say anything? I have since just gone back to burning single drives and honestly it's fine. Ventoy was convenient but taking a year to respond to a genuine concern is crazy.

    [–] rtxn@lemmy.world 4 points 3 days ago* (last edited 3 days ago) (2 children)

    I'm going to guess you've never been part of a project with complexity and sheer black magic fuckery comparable to Ventoy. The developer (a singular person) had to make a choice between:

    • Pandering to a small group of vocal open-source extremists, dedicating a large part of their time to changing the incredibly complex build process to also build the binaries of other open-source projects, potentially at the cost of stability, eventually arriving at a product with the same feature set, pleasing some open-source extremists, but still receiving criticism for "taking a year to respond to a genuine concern"; or
    • Not doing that and focusing their effort on stability and compatibility fixes to arrive at an improved product.

    I've read the original issue thread front to back, and it's a fucking clown show. I can't blame the developer for not wanting to engage with those people. Nobody is entitled to the developer's time or attention. Right now the issue is being worked on, which is more than most of the whiners can say about themselves; if you think that's still insufficient, do better.

    [–] Agent641@lemmy.world 1 points 3 days ago

    Mr Ventoy has too many problems

    [–] Turret3857@infosec.pub 0 points 3 days ago

    I don't think a simple statement of "I see your concern, I'll address it when I have time" is really that hard for one person to issue when the alternative is, as you've said, letting "a fucking clown show" fester on. It would've made my worries go away if the developer had said literally anything instead of radio silence for a year. Sure, no one is entitled to a developers time or attention. That developer is also not entitled to my trust or recommendation to others when a serious issue was swept under the rug for over a year. There's no doing better when it comes to a matter of personal opinion on how a situation was handled.

    [–] Tundra@lemmy.ml 22 points 5 days ago (2 children)

    just started using this for the first time, Is it still ok to use?

    [–] rtxn@lemmy.world 62 points 5 days ago* (last edited 5 days ago) (2 children)

    Yes, but people have concerns. Ventoy is fully open-source, but the build process pulls binary blobs (compiled executables, think of them like blob chips) from other F/OSS projects, which is an issue for some people. They have legitimate concerns about trusting Ventoy because they have to implicitly trust the projects that Ventoy pulls from but can't verify what is getting pulled. If such a project were to become compromised (the way XZ-Utils was), it would eventually spread to Ventoy.

    That being said, the developers (or singular developer, not sure) are taking steps to reduce Ventoy's dependency on external blobs. It's a difficult task and they have limited resources, but they have acknowledged that it is an issue and are working on a solution.

    [–] unhrpetby@sh.itjust.works 34 points 5 days ago* (last edited 5 days ago)

    If such a project were to become compromised (the way XZ-Utils was), it would eventually spread to Ventoy.

    What a lot of people don't know is that the XZ attack entirely relied on binary blobs: Partially in the repo as binary test files, and partially in only the github release (binary).

    If someone actually built it from source, they weren't vulnerable. So contrary to some, it wasn't a vulnerability that was in plain view that somehow passed volunteer review.

    This is why allowing binary data in open-source repos should be heavily frowned upon.

    [–] possiblylinux127@lemmy.zip 2 points 4 days ago

    I don't believe iVentroy (PXE tool) is fully foss but I could be wrong.

    [–] slazer2au@lemmy.world 19 points 5 days ago (1 children)

    Yea it's fine.

    From memory the blob everyone was complaining about was related to eufi and came from Fedora.

    [–] possiblylinux127@lemmy.zip 3 points 4 days ago

    Except for the part where it completely nullifies secure boot...

    Fine if you don't care about that but it caused a lot of security issues in the enterprise

    Just open source blobs instead of proprietary blobs

    [–] Lucien@mander.xyz 12 points 5 days ago

    Off topic, but I'd never heard of Ventoy before and looking at it now, holy shit, I wish I'd known about it sooner.