Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)GE
gedhrel @ gedhrel @lemmy.world
Posts
0
Comments
128
Joined
2 yr. ago

If anything happen to Linux today, like what happened to Windows, most of the internet would be dead.

Jump

  • ...unless it's running software that uses signed 32-bit timestamps, or stores data using that format.

    The point about the "millennium bug" was that it was a category of problems that required (hundreds of) thousands of fixes. It didn't matter if your OS was immune, because the OS isn't where the value is.

    • To those with 2+ monitors on your machine: What's your use case, and how much does it actually boost your productivity?

    Jump

  • Fab, cheers.

    • To those with 2+ monitors on your machine: What's your use case, and how much does it actually boost your productivity?

    Jump

  • Dare I ask what the adjective "hella" means in this context?

    • The Xz Backdoor Highlights the Vulnerability of Open Source Software—and Its Strengths

    Jump

  • The test case purported to be bad data, which you presumably want to test the correct behaviour of your dearchiver against.

    Nothing this did looks to involve memory safety. It uses features like ifunc to hook behaviour.

    The notion of reproducible CI is interesting, but there's nothing preventing this setup from repeatedly producing the same output in (say) a debian package build environment.

    There are many signatures here that look "obvious" with hindsight, but ultimately this comes down to establishing trust. Technical sophistication aside, this was a very successful attack against that teust foundation.

    It's definitely the case that the stack of C tooling for builds (CMakeLists.txt, autotools) makes obfuscating content easier. You might point at modern build tooling like cargo as an alternative - however, build.rs and proc macros are not typically sandboxed at present. I think it'd be possible to replicate the effects of this attack using that tooling.

    • Non-root user that (suddenly) has elevated privileges in a specific command (only). [Have I been hacked?]

    Jump

  • What are the permissions on the directory? What is command are you running to edit the file? What command are you running to delete it? (Have you got selinux turned on? What filesystem is this directory on?)

    • Why Git is hard

    Jump

  • It's all the files. Content-addreasable storage means that they might not take up any more space. Smart checkout means they might not require disk operations. But it's the whole tree.

    • Why Git is hard

    Jump

  • Came here to say the same thing. The git book is an afternoon's reading. It's well worth the time - even if you think you know git.

    People complain about the UX of the cli tool (perhaps rightly) but it's honestly little different from the rest of the unix cli experience: ad hoc, arbitrary, inconsistent.

    What's important is a solid mental model and the vocabulary of primitive and compound operations built with it. How you spell it in the cli is just a thing you learn as you go.

    • Probably a stupid question, but will we ever have something like a microwave to make things cold? Is there a reason this can't exist?

    Jump

  • Came here to mention laser cooling; glad someone else got there first.