InEnduringGrowStrong@sh.itjust.works

For anything important, use matrix instead of lemmy DMs.

  • 0 Posts
  • 76 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle











  • OP is a racist jumping through alt accounts. In their mind, they’re making of fun of some imaginary dissonance between people liking the person in the top image and not liking the person in the bottom image.

    They only ever see through the perspective of a racist.
    In their tiny mind, “other race = inherently bad”, so to them, non-racist people must surely be going… “other race = inherently good”.

    To them, race here was some magic card they can pull out as a gotcha, as if we should like Musk because he’s African.

    Their little brain cannot fathom we might dislike Musk because he’s a billionaire narcissist sociopath and not because he was born in Africa.




  • The problem is there’s likely not a universal solution that’s guaranteed to clean everything in every case.

    Cleaning specific logs/configs is much easier when you know what you’re dealing with.
    Something like anonymizing a Cisco router config is easy enough because it folllows a known format that you can parse and clean.
    Building a tool to anonymize some random logs from a specific software is one thing, anonymizing all logs from any software is unlikely.
    Either way, it should always be double-checked and tailored to what’s being logged.


  • It depends a lot on what the application is logging to begin with.
    If a project prints passwords in logs, consider to just GTFO as it’s terrible security practice.
    There might also be sensitive info that’s not coming from a static thing like your username, but from variable data such as IP addresses, gps coordinates, or whatever thing gets logged.
    Meaning a simple find&replace might be insufficient.

    When possible, I tend to replace the info I remove with a short name of what I replaced out as it’s easier to understand context when it’s not all ********** or truncated.
    example:

    proxy_container_1     | <redacted_client1_ip> - - [17/Aug/2024:12:39:06 +0000] "GET /u/<redacted_local_user2> HTTP/1.1" 200 963 "-" "Lemmy/0.19.4; +<redacted_remote_instance3_fqdn>"
    

    keeping the same placeholders for subsequent substitutions helps because if everything is the same, then you don’t know what’s what anymore.
    (this single line would be easy enough either way, but if you have a bunch and can’t tell client1 from client50 apart anymore that can hinder troubleshooting.

    regular expressions are useful in doing that, but something that works on a specific set of logs might miss sensitive info in another.

    I’m sure people have made tools to help with that, possibly with regex patterns for common stuff, but even with that, you’d need to doublecheck the output to be 100% sure.

    It helps a lot when whatever app doesn’t log too much sensitive info to begin with, but that’s usually out of your hands as a user.