• 4 Posts
  • 56 Comments
Joined 2 years ago
cake
Cake day: October 15th, 2023

help-circle
rss






  • I used to do the same thing to a few people back in the day. Linux distros used to ship with the X listening port just conveniently wide open and the config set to allow input from any other device on the LAN. I’d start with only one xeyes, and then they’d close it. I’d do it a few more times until they got irritated with me, and then I’d push it further by putting xeyes into a bash loop to open dozens at a time.


  • I wrote a simple script once that ran in the background and all it did was toggle the state of the caps lock key every 30 minutes. I set it up on a co-worker’s computer as a scheduled task for an April Fools prank one year. I thought for sure he’d figure it out pretty quickly, but by mid-day, he had completely disassembled his keyboard, convinced the button was getting stuck due to gunk buildup. Eventually I ended up just disabling the task so he thought he had managed to fix it himself.












  • I would say not much. If it’s your own personal LAN, and only your devices are on it, and you’re not hosting super sensitive data, then I wouldn’t personally be worried. Just depends on your risk acceptance.

    Edit: But if you are hosting sensitive data on an untrusted network, then definitely require a user with a strong password. Also, SMB3 and higher supports encryption (both in Windows and Samba for Linux). Encryption isn’t enabled by default, though. So keep that in mind. Easy to setup on both Windows and Linux.


  • That’s a security quirk. Microsoft reeeeeally doesn’t want you to do anonymous SMB anymore, and with every version of Windows, Microsoft has made is more complicated to get it working like that. It’s probably still possible, but easier just to make a quick local user account and assign it read/write permissions to the share. Samba on Linux can still do it without as much fuss, but I’ve long since just accepted the extra step.