Also, don't expose windows shares to the internet.
Is this a problem? I feel like this reputation is 10 years out of date.
Personally I use smbd & I am not afraid for it. I'd like to tell Windows users the dame, provided I trust them to disallow all but logged in users.
1. Harden the operating system
2. Actively monitor logs, and apply updates upon release
3. Put a Firewall with IDS/IPS between the server and the internet (which most home "routers" do not provide)
you should not put anything on the wider internet, instead using something like tailscale (which you mention in another post) to create a secured private network across unsecured inet
I've gone through every CVE for Samba & there seemingly is 1 potential problem since 2007 that would possibly potentially be an issue for a basic non-domaim controller smbd fileshare that a random non-user could possibly exploit. If you dont trust your users, there's indeed some CVEs of real threat, but still, like... 4.. https://www.cvedetails.com/vulnerability-list/vendor_id-102/...
Yes you probably should update fairly regularly, just in case. But more often than not, if you are a couple years behind, it's not a problem. Maybe someday that goes bad. But... so far... being super lax on updates generally hasnt had much impact. Maybe check logs every now and then, but honestly... once you have some confidence, it's fine. This stuff runs fine. It's easy.
(at least compared to caddy or wireguard...)
https://www.bleepingcomputer.com/news/security/smb-zero-day-...
https://www.computerworld.com/article/2513099/new-windows-ze...