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

help-circle



  • You should take notes about how you set up each app. I have a directory for each self hosted app, and I include a README.md that includes stuff like links to repos and tutorials, lists of nuances of the setup, itemized lists of things that I’d like to do with it in the future, and any shortcomings it has for my purposes. Of course I also include build scripts so I can just “make bounce” and the software starts up without me having to remember all the app-specific commands and configs.

    If a tutorial gets you 95% of the way, and you manage to get the other 5% on your own, write down that info. Future you will be thankful. If not, write a section called “up next” that details where you’re running into challenges and need to make improvements.







  • 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.)