• 3 Posts
  • 246 Comments
Joined 10 months ago
cake
Cake day: August 22nd, 2024

help-circle








  • Every worker moved is another worker more likely to use Linux at home. In my experience you’re most likely to use the computers you work with (school or otherwise) and exposure to Linux is going to demystify it in ways social media cannot.

    Most exciting is probably the IT management side. I wonder how many distros are hardened for end users who do general office work - where people are more likely to tinker and mess about either for fun or to optimise things.






  • My scepticism is that this should’ve been done within the coreutils project, or at least very closely affiliated. This isn’t an area of the linux technical stack that we should tolerate being made distro-specific, especially when the licensing is controlled by a single organisation that famously picks and chooses its interpretation of “FOSS” to suit its profit margins.

    On a purely technical level, GNU coreutils should very seriously consider moving to rust if only to counter alternatives before it’s too late. While these utilities work well in C (and usually stay secure thanks to the Unix philosophy limiting the project scope), FOSS projects are continuing to struggle with finding new contributors as younger devs are more likely to use modern systems languages like Go and Rust. Not to mention that any project using Rust as a marketing tool will appeal to anyone rightfully concerned about hardening their system.





  • Hector and others were really bad losses for the Rust kernel devs but Lina? That’s catastrophic. She was a figurehead in getting apple silicon working so well on Linux that even Linus moved his development machine to an M1 Macbook.

    Linus has royally fucked it with how long he sat on the side of this. Im so sorry to Lina and others who have been burned by this community.


  • True, any software can be vulnerable to attack.

    but the difference is a technical team of software developers can mitigate an attack and patch it. This guy has no tech support than the AI that sold him the faulty code that likely assumed he did the proper hardening of his environment (which he did not).

    Openly admitting you programmed anything with AI only is admitting you haven’t done the basic steps to protecting yourself or your customers.




  • Short answer: Yep, cheat softwares regularly do this too, but it’s costly and prone to being immediately patched, and it’s potentially illegal.

    Anticheat systems are designed around this since a cheat client would try to do exactly that. One way for example is for the anticheat to provide a cryptographic key to the game which it uses to prove to a multiplayer server that the anticheat is functioning and untampered with. Even if you bypass anticheat locally, you still have to prove that the game client is legitimate to the server. This does happen! But kernel anticheats are much harder to access and tamper with, and in our case of using WINE are unlikely to even work from the outset.

    So okay, let’s hypothetically bypass anticheat locally. We modify the game to tell the server it’s legit, and it works! A few days later the game gets patched, and suddenly our bypass is defunct. For cheat sellers this part of the cost of business but for people just trying to game on Linux there’s little money in it, and if there is it won’t ever be spent on circumventing anticheat (which also falls under some legal grey areas if not outright illegal depending on your country).

    Given enough time and resources we could probably find some novel way to crack anticheat on a game as such as it becomes playable on Linux. But it’s so much easier to use that effort somewhere else or just use a Windows VM that is guaranteed to work even if slightly slower.