• lmmarsano@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    2
    ·
    edit-2
    7 hours ago

    OP thinks security researchers don’t understand how to properly serialize data for correct deserialization. OP also thinks they largely use CSV.

  • muusemuuse@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    6 hours ago

    Guys calm the fuck down. The point of this joke is not that you’ll be bulletproof a few in sort of a few commas and passwords every now and then. The point is that a lot of these guys use terrible scripts that do not parse data correctly and they dump all of this shit into large CSV files. One or two people put an errand, in there that it doesn’t expect and it fucks the whole thing sideways for the entire set everything after the asshole with the comma password gets fucked. People that know what they’re doing will be just fine with it, but scammers generally don’t know what the fuck they’re doing and they pass this data along over and over and over again it change his hands frequently. So there’s more chances for it to get fucked along the way.

  • kryptonianCodeMonkey@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    4 hours ago

    Correct me if I’m wrong, but doesn’t text with commas in it get put in double quotes in acsv file to avoid this exact thing?

    Like if I had cells (1A: this contains no comma), (2B: this, contains a comma), and (3C: end of line), the csv file would store (this contains no comma,“this, contains a comma”,end of line)

    • Wolf314159@startrek.website
      link
      fedilink
      arrow-up
      2
      ·
      3 hours ago

      A CSV is just a long string of text with a few control characters tossed in for end lines. There are practically no rules enforced by the file type itself. You can dump that unsanitized and poorly awk’d data into whatever awful mess you want. Nobody’s stopping you. Sure, excel will force it’s CSV formatting rules on you when you export like a child’s training wheels. But that’s not relevant here.

    • patrick@lemmy.bestiver.se
      link
      fedilink
      English
      arrow-up
      14
      ·
      9 hours ago

      Yes and no. Like yes, that can be true. But a lot of tools don’t handle commas correctly no matter how you escape them.

    • nandeEbisu@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      8 hours ago

      You would be surprised how many people are simply splitting the string on commas instead of using an actual ascii parser. Especially for one off scripts, like churning through a csv full of passwords.

    • BodilessGaze@sh.itjust.works
      link
      fedilink
      arrow-up
      19
      ·
      12 hours ago

      CSV existed for over 30 years before RFC 4180. Excel, and countless other tools, have their own incompatible variants. Excel in particular is infamous for mangling separators when exporting to CSV.

      • ChaoticNeutralCzech@feddit.org
        link
        fedilink
        English
        arrow-up
        19
        ·
        11 hours ago

        Fuck Excel’s CSV handing. It differs by locale, silently. Imagine the thousands of people every year who patiently wait to import a multi-megabyte CSV from some instrument only to see garbage because their language uses the decimal comma and semicolon separator.

    • 𝕛𝕨𝕞-𝕕𝕖𝕧@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      edit-2
      13 hours ago

      yeah unless you’re dealing with some steaming pile of vibe-coded shit this is a dumb as fuck idea.

      (have seen people who don’t know how to appropriately use an LLM just let it wholly reimplement standards, read it over, and then say “oh wow that works great!” smh…)

        • 𝕛𝕨𝕞-𝕕𝕖𝕧@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 minutes ago

          of course there’s always been terrible code. people used to and still do reinvent the wheel all the time, even without the help of a robot.

          trust me i’m one of the last people to shit on LLMs unnecessarily. the tools coming out nowadays are the bees knees. i think vibe coding is fucking awesome and most people’s premonitions against it are things that, similar to the premise, have just always been true - most of the “evil” of vibe coding can be dealt with easily by being a not shit engineer in the first place.

          plus, not every problem needs to be a software development problem through and through. sometimes you just need a webui or an api to browse a dataset, for example - it’s not opsec critical and you need it now. that’s okay. the moral police won’t come to your house and arrest you for vibe coding.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    220
    ·
    20 hours ago

    Use EICAR test strings as passwords so when the password is stored as plain text the antivirus software will delete the file.

    • Orygin@sh.itjust.works
      link
      fedilink
      arrow-up
      18
      ·
      14 hours ago

      Sadly it wouldn’t work if found in a CSV file with other records:

      According to EICAR’s specification the antivirus detects the test file only if it starts with the 68-byte test string and is not more than 128 bytes long. As a result, antiviruses are not expected to raise an alarm on some other document containing the test string

      • slazer2au@lemmy.world
        link
        fedilink
        English
        arrow-up
        62
        ·
        20 hours ago

        Doesn’t have to be a binary file, toss the string in a txt file and the AV still throws a fit.

      • NatakuNox@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        13 hours ago

        01001000 01100101 01101100 01101100 01101111 00101100 00100000 01110100 01101000 01101001 01110011 00100000 01101001 01110011 00100000 01101110 01101111 01110100 00100000 01100001 00100000 01110011 01110100 01110010 01101001 01101110 01100111 00100000 01101111 01100110 00100000 01100010 01101001 01101110 01100001 01110010 01111001 00100000 01110100 01101000 01100001 01110100 00100000 01110100 01101111 01110100 01100001 01101100 01101100 01111001 00100000 01110111 01101111 01101110 00100111 01110100 00100000 01101001 01101110 01100110 01100101 01100011 01110100 00100000 01111001 01101111 01110101 01110010 00100000 01110000 01101000 01101111 01101110 01100101 00100000 01101111 01110010 00100000 01100011 01101111 01101101 01110000 01110101 01110100 01100101 01110010 00100000 01110111 01101001 01110100 01101000 00100000 01100110 01110101 01110010 01110010 01111001 00100000 01110000 01101111 01110010 01101110 00101110 00100000 01010100 01101000 01100001 01110100 00100000 01101001 01110011 00100000 01100001 01101100 01101100 00101110 00101110 00101110 00100000 01000100 01101111 01101110 00100111 01110100 00100000 01100011 01101000 01100101 01100011 01101011 00100000 01101001 01101110 01110100 01100101 01110010 01101110 01100001 01101100 00100000 01110011 01110100 01101111 01110010 01100001 01100111 01100101 00101110 00100000 01010100 01101000 01100001 01101110 01101011 00100000 01111001 01101111 01110101 00100000 01111000 01101111 01111000 01101111

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      22
      ·
      19 hours ago

      Unfortunately there is significant overlap between plain-text-password-servers and servers that can’t be bothered to use antivirus. Also, the string may not work if it’s not at the start of the file. AV often doesn’t process the whole file for efficiency purposes.

      • B-TR3E@feddit.org
        link
        fedilink
        arrow-up
        46
        ·
        19 hours ago

        It’s not about the password on the server where you want to log in, it’s about CSV files stored on the machine of the cybercrook who wants to use the passwords to steal people’s identities.

    • Lucy :3@feddit.org
      link
      fedilink
      arrow-up
      3
      ·
      13 hours ago

      According to EICAR’s specification the antivirus detects the test file only if it starts with the 68-byte test string and is not more than 128 bytes long.

      Unless you’re the only one in the dump, no :c

    • Saganaki@lemmy.zip
      link
      fedilink
      arrow-up
      11
      ·
      20 hours ago

      unfortunately, nearly all AV abides by the “cannot be larger than 68 bytes” rule

  • AnimalsDream@slrpnk.net
    link
    fedilink
    English
    arrow-up
    5
    ·
    11 hours ago

    Use a long series of spaces as your password. At least that way they’ll have to do a double take when they crack the hash.