You should probably tell people why is this release newsworthy, otherwise people might as well just subscribe to the Pipewire changelog.
- 0 Posts
- 5 Comments
The issue is that for the FSF, what they call “software freedom” is their number one goal. So what’s likely to happen is that they create some kind of “deblobbed” firmware that breaks many features and security of the device, which Graphene OS will refuse to use.
I hope this project will be useful but am worried that they’ll just make a shittier version of someone else’s work like they did with e.g. Libreboot.
Cool! I might install something like this someday.
Do you use secure boot? What device is your server? I would use my laptop for that, but not sure if that’s how it should work.
TMP_NKcYUEoM7kXg4qYe@lemmy.worldto Linux@lemmy.ml•The dangerous push by Canonical to rewrite GNU coreutils as Rust code without the GNU license0·2 months agoThe title is bs. There is no “push by Canonical”. A random person on the internet wrote Uutils in Rust because it’s easy to write fast code in it. Then Canonical wants to package the software but they aren’t “pushing”, they are just packaging software someone else wrote. Canonical’s goal is memory safety but that’s not the author’s goal because Coreutils haven’t got many vulnerabilities anyways.
The licensing part is sort of sad. The author picked MIT, because he does not care. He also said that he does not want drama. Well he did get the drama. The sad part is that I think that he would be willing to change the license to GPL, had it not been for all the childish drama and “hate”. Communication is difficult for people online, unfortunately.
Brodie Robertson made a video about malware which pretends to be a pdf but is actually just an executable with a
.pdf
file extension. So if you double click it, you get pwnd. I think some desktop environments ask you for confirmation before running such thing but I would not count on it.So we even have an example of Linux specific malware.