rummaging around in /etc felt really limiting.
Sorry, I didn't get this. Could you elaborate?
rummaging around in /etc felt really limiting.
Sorry, I didn't get this. Could you elaborate?
their limitations make many things a person may eventually want to do with their machine a lot more complicated.
Like what?
Would anyone that installed their current system using ventoy be at risk?
In absolute sense; we don't know for sure. It's possible to interpret this^[i.e. The lack of communication regarding this issue for more than a year, the recent finding in which fake root certificates are injected. And, of course, the maintainer finally addressing the issue.] in widely different ways:
Should I reinstall?
You should make up your own mind on that. The last time I installed an OS, I had become aware of this concern (i.e. the blobs). At that time, trusting it for what it was, would go against the threat model I've set for myself. And, consequently, if I had any (other) systems that were installed with it, then I would have proceeded to reinstall. But I'm not you, nor are you me... So, at the end of day, if you had something that resembled a threat model, then you would have used that to answer this question for yourself. As you don't seem to have one, making one just for this seems overkill. However, you could (re)assess how safe your system is in its current state and act accordingly. (Just to name a couple of examples:)
Assuming you're finally done with your edits^[Btw, I absolutely loved to witness the diligence you put into your craft. Thank you for the effort! It also reminds me of the times I do something similar. Though, fam, don't forget to think about yourself; you're important to us 💙!] (the transition from 0 -> 1 likes is the only thing I'm going off of), I think your comment is overall just a work of art; attempting to add anything on/to it feels like tarnishing it. Though, a major correction is due: The "the return of Ventoy's maintainer"-remark was meant to convey their return to the issue. I didn't want to imply that they left the project and returned. Though I totally understand the confusion; my apologies*. Furthermore, my striped remark was actually somewhat meant as a joke - I hoped that blatantly stating "The conspiracy theorist inside of me would like to think" was enough of a hint for that - but I totally get where the misunderstanding is coming from.
Anyhow, if anything, I hope that we'll be met with a solution that's compliant with your suggested solution (or better if possible). Nonetheless, I would like to voice my appreciation for this lovely interaction! Thank you!
I was trying to stir a discussion/conversation: How much can we tolerate from our beloved (F(L))OSS developers? Can they get away with anything as long as they return with some promise?f
The fact remains though: why did they literally go radio silence on this issue for over a year? Like, a simple, "I would like to notify everyone that I'm working on this." would have been sufficient. Was that too much to ask?
To me, what matters is what guarantees they offer and/or plan to offer,
Let's indeed hope that they back it up with action. Better late than never. Though, I wonder what "guarantee" you're referring to.
FWIW, slightly over a month ago, someone started working on a solution. ~~The conspiracy theorist inside of me would like to think this is related to the return of Ventoy's maintainer. But I digress...~~
I'll try to keep it brief/concise/short. Apologies if this makes me come across as abrasive in the process.
If I'd attempt to distill the point(s) in your reply, I'd come to:
The guy is trying to address the issue and he is building this in his free time. Give him some credit at least, I am sure this is consuming a lot of his free time.
Fam, you've chosen to trust them for reasons that are unclear to me. Honestly, I don't see anything (yet) that would clear their name. For all we know, they could have ties to some intelligence agency; which the infamous Jia Tan has (retroactively) been accused of as well.
I personally find this Ventoy an amazing piece of software
That's not the issue. I've also made plenty use of it in the past. But at what point do you start to second guess the intent behind the maintainer?
he also seems to be willing to address the issue and be more transparent in the future which is also commendable.
Again, arguably too little too late. They literally ghosted the issue for over a year. Then, within 24 hours of possible proof of malicious code, they appear and (perhaps) "pose the image" of putting in a gargantuan effort to resolve the issue. But, like, where were they for a year? Furthermore, the hints of justifications for their actions are simply not up too par.
Don't get me wrong. As I clearly hinted at it in my previous comment, if they pull through and provide/produce (bit-by-bit) reproducible builds of Ventoy^[Another spoiler-alert: They admitted that it would be hard. Which is fine, but could be interpreted as the first action for an eventual cop out. Only time will tell...], then I obviously have no qualms against them or their software. Why would I? But until then, I will steer clear.
What should have happened for you to be more concerned?
Perhaps I'm too skeptical and/or have trust issues, but isn't this too little too late? This issue had been ignored for so long, but -suddenly- within 24 hours of this very peculiar find^[Spoiler alert: Ventoy's sister software -called iVentoy- employs a trick that has been utilized for installing compromised kernel drivers.], Ventoys maintainer goes into full damage-control mode. Should we just accept that?
Sorry, at least for now, I simply don't buy it.
I do think uBlue is downstream
It's indeed downstream~ish. But perhaps just different enough to actually make a meaningful change.
Sorry, I think there's a misunderstanding.
First of all, thank you for clarifying what you meant. I'm not native, so I haven't seen "rummage" being used within that context. And while a LLM did (at least an attempt to) provide its meaning, it didn't make sense... by which we have arrived at the misunderstanding.
Yes, for Fedora Atomic, (most of)
/usr
is read-only. Perhaps this also applies to some other folders of/
, however this doesn't apply to/etc
as it's not read-only; therefore, you can actually change its content. At best, you'd have to gosudo
(or fill the credentials through polkit's window); but that's all. This part isn't different from how it's over on (traditional) Fedora. Compared to its non-Atomic variant, however, we do find the following changes regarding/etc
:/etc
are being kept track of. You can access these throughostree admin config-diff
./etc
is kept at/usr/etc
. And, that one, is actually read-only.So..., the following step, i.e.
Isn't required or anything. Heck, it's the first time (after three years of Fedora Atomic) that I've seen something like that being mentioned within this context.