• sylver_dragon@lemmy.world
    link
    fedilink
    English
    arrow-up
    52
    arrow-down
    1
    ·
    2 days ago

    Sadly, no. CSV files can deal with embedded commas via quoting or escaping. Given that most of the dumps are going to be put together and consumed via common libraries (e.g.python’s csv module), that’s all going to happen automagically.

      • ilinamorato@lemmy.world
        link
        fedilink
        arrow-up
        14
        ·
        2 days ago

        Everything you can use for a password can be escaped out of a csv. Partially because csvs have to be interoperable with databases for a bunch of different reasons, and databases are where your passwords are stored (though ideally not in plaintext). There’s no way that I can think of to poison your password for a data breach that wouldn’t also poison the password database for the service you’re trying to log into.

        • bassomitron@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          2 days ago

          Gotcha, that’s what I was thinking as well. I haven’t done any software development in a long time (I have a degree in it, but professional career sent me down another path in tech), so my memory on input sanitization is very rusty. Thanks for the response!

    • nymnympseudonym@piefed.social
      link
      fedilink
      English
      arrow-up
      22
      ·
      2 days ago

      Can be != will be

      You’re looping over 50M records, extracting into your csv. Did you bother using the appropriate library, or did your little perl script just do split(/,/,$line)