• 0 Posts
  • 288 Comments
Joined 2 years ago
cake
Cake day: June 19th, 2023

help-circle



  • In 1999+ you could sniff people’s passwords in clear text right out of the air on public WiFi networks. tcpdump port 110 and just watch them roll in.

    In the late 90’s you could use a floppy disk to boot nt and dump the password hashes of anybody who had logged in, then run them through a dictionary attack which would take a matter of minutes before learning that your company’s top employees used their favorite football team or cartoon character as their password without even appending some numbers to it. Dude with the football password even had the password emblazoned in his office wall.

    One time in the 90’s I got to a password prompt and just held enter, and eventually was just let past the password prompt.

    In X windows if you managed to kill the screensaver password entry box you were dropped back to the desktop, and people found ways to crash the screensaver by overrunning the password input buffer by pasting input repeatedly using common keyboard shortcuts. (Pretty sure this same exact bug exited in early Mac osx versions.)


  • Before the cloud it was so hard to get a budget for anything, even necessary yearly upgrades. Sometimes I would have to scrap the least important server when a component in a more important one died. Then the cloud came along and suddenly we had so much money to spend! But now it was so hard to track who spent it, what projects it was spent on, and how we could dial it down. SMH. Cloud computing can be so ridiculous.












  • One big problem with GitHub that is only briefly touched on in the article is that developer teams used to be able to use the feed to get useful updates on what their team was working on. Now, it’s polluted with unrelated AI generated suggestions. So for those of us who use Github as an enterprise application, we previously had a user friendly app that helped us get work done, but we now have a user hostile app that participates in the attention economy, luring us with distractions, which are the opposite of what we should be doing at work. The GitHub feed is now anti-focus, anti-work, algorithmic buzz, and enterprises like my employer still pay for that.




  • Run strace (or falco) and log every file open. When you hear the sound, reference the log of what files were accessed at that time.

    Run tcpdump and capture all traffic. Analyze it in wireshark, searching for a time window around when the sounds happened.

    FWIW putting pranks like this in cron or systemd is a common way to haze people who have bad security practices. We also used to set the default run level to 3 or 6, but of course that doesn’t make sense in the era of systemd.