• 1 Post
  • 318 Comments
Joined 1 year ago
cake
Cake day: January 3rd, 2024

help-circle

  • It’s you can modify the settings file you sure as hell can put the malware anywhere you want

    True. (But in case it amuses you or others reading along:) But a code settings file still carries it’s own special risk, as an executable file, in a predictable place, that gets run regularly.

    An executable settings file is particularly nice for the attacker, as it’s a great place to ensure that any injected code gets executed without much effort.

    In particular, if an attacker can force a reboot, they know the settings file will get read reasonably early during the start-up process.

    So a settings file that’s written in code can be useful for an attacker who can write to the disk (like through a poorly secured upload prompt), but doesn’t have full shell access yet.

    They will typically upload a reverse shell, and use a line added to settings to ensure the reverse shell gets executed and starts listening for connections.

    Edit (because it may also amuse anyone reading along): The same attack can be accomplished with a JSON or YAML settings file, but it relies on the JSON or YAML interpreter having a known critical security flaw. Thankfully most of them don’t usually have one, most of the time, if they’re kept up to date.







  • Today I learned the term Vibe Coding. I love it.

    Edit: This article is a treasure.

    The concept of vibe coding elaborates on Karpathy’s claim from 2023 that “the hottest new programming language is English”,

    Claim from 2023?! Lol. I’ve heard (BASIC) that (COBOL) before (Ruby).

    A key part of the definition of vibe coding is that the user accepts code without full understanding.[1] AI researcher Simon Willison said: “If an LLM wrote every line of your code, but you’ve reviewed, tested, and understood it all, that’s not vibe coding in my book—that’s using an LLM as a typing assistant.”[1]

    Did we make it from AI hype to AI dunk in the space of a single Wikipedia article? Lol.




  • Yes, that’s the joke.

    AI creates almost (but not) good enough stuff really fast. And occasionally straight up hallucinates stuff that is meaningless or worse.

    So this person has a huge stack of functional but broken crap, and it’s blaming X for their woes.

    There’s an old saying that goes roughly “It takes four times the experience to maintain a program as it took to write it. So anyone writing the most clever program they can think of is, by definition, not competent to maintain it.”

    In this case, it’s extra funny, because neither the AI nor the AI user has the faintest idea how the generated code works. So maintaining it is almost certainly 1000% outside their abilities.

    So they’ve paid an AI for the privilege unpleasant daily panic of learning everything they need to learn after the app has gone to production, rather than before.