Not for a company with 120 Billion profits.
Not for a company with 120 Billion profits.
“HEY, I’M LOOKING FOR [hidden network name]”
Client devices can also do this all the time even when not in range, which basically broadcasts they’re looking for that network everywhere they go. That’s just asking for someone to setup a rogue access point.
“GIVE US ALL YOUR MONEY NOW OR WE ARE DRIVING YOU OFF THE GRAND CANYON"
Can I just skip straight to this part?
RAM is cheaper than my time.
I kinda consider 32GB as a minimum for anyone working on my team.
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.
Haven’t had to use port forwarding for gaming in like 30 or so years, so I just looked up Nintendo’s website…
Within the port range, enter the starting port and the ending port to forward. For the Nintendo Switch console, this is port 1024 through 65535
LMAO, no thanks, that’s not happening.
For your question, you could likely route everything through a tunnel and manage the port forwarding on the other end of the tunnel.
Hijacking twitter DNS queries and redirecting to a page that only serves images of cats.
Twitter already sucked in its own ways, but X-formerly-known-as-twitter is so utter shit I have a hard time imagining people browsing and enjoying it.
Yea, but if you have your own OC devastation, you can broadcast your gofundme scam or whatever.