• 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: October 15th, 2023

help-circle
  • Sums up every conversation I’ve had where a Windows person has told me they won’t use Linux because of how complicated it is. Sure, Windows may be easier initially, up until the point that something decides not to work, and then you’re left tracking down obscure forum threads and blog posts. You check event logs, and there’s either nothing relevant, or you find an event that just sums up the exact error you already saw. Microsoft’s own support forum is just a graveyard of threads ending in “please run sfc and/or dism”. Contrast that with open source logs, for the most part, you’ll know what the problem is just from reading through the output. It’s usually not pretty, and boy is it a lot of log messages, but at least you’re not completely in the dark. And I mean this for both server and personal computer usage. Microsoft just has a terrible track record with being verbose about errors.





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