“GIVE US ALL YOUR MONEY NOW OR WE ARE DRIVING YOU OFF THE GRAND CANYON"
Can I just skip straight to this part?
“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.
Yea I miss the hardware fingerprint reader that was on my last one. The under screen reader is much slower and less reliable.
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.
Problem solved
I’d love to switch between shooting blanks and livefire on-demand.
Yea, I’m still stuck on Windows at work for the foreseeable future as I don’t control that too much.
Otherwise, for personal stuff that I do control, they really can get fucked.
My wife had never used any desktop OS other than Windows before, but I switched her to Pop!_OS and it’s gone fine. Certainly not any worse than between 2 Windows versions, but at least now there’s no bullshit and things are actually customizable. (Her words)
This is the same kind of thing I’d expect when a once nice android app gets bought out by a company like tencent.
Bundle a battery manager and RAM optimizer bs in the file browser or something, fill it with ads, maybe they could have microtransactions for some of the “features”.
They do, but something like fucksmith’s pizza would be upvoted for being funny, not for being correct.
The LLM wouldn’t know the difference.
This post is 2 days old, we are now officially old people.
Yup. On reddit, if you stumbled on a 13 hours old thread, commenting was just sending a bottle in the void.
LTSC is great.
Much less bloat and bs too.
end up with people who don’t recognize that 13+24=87 is incorrect
I had a telecom teacher who would either allow you to use a calculator, but you had to get everything right.
Or go without and you could get away with rougher estimates.
Doing stuff like decibels by hand isn’t too bad if you can get away with a ballpark and it’s a much more useful skill to develop than just punching numbers in a calculator.
Haven’t used LVM in a while, so I can’t offer much insight there other than consider taking a backup of anything important.
I mean if there are severance packages, I wouldn’t say no.
Make sure you backup your vault and/or keep the backup “paper codes” somewhere safe.
Aegis, for example, can automatically backup an encrypted vault.
On top of all the other good answers, someone can also just SIM hijack your phone number by social engineering your phone provider into activating a new SIM card.
And it’s usually much easier than one would think/hope.
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.