Time Machine support is also dropping support over SMB1 so whatever new solution needs to support SMB2/3.

jychang 7 minutes ago | parent | next [-]

I've added support for Samba 4 (running SMB3) to the Time Capsule so it can work with modern macOS: https://github.com/jamesyc/TimeCapsuleSMB

▲

stackskipton 6 hours ago | parent | prev | next [-]

SMB2 came out with Vista and SMB3 was Win8 so they are not new protocols either.

	▲	winocm 5 hours ago \| parent [-]
		That just ended up inadvertently reminding me, Windows Vista is actually almost old enough to be at the minimum legal drinking age in the US. Windows 8 is nearly a decade and a half old as well. Time really does fly.

▲

wtallis 6 hours ago | parent | prev | next [-]

Where "new" in this case could be a NAS running Samba from 2011? Samba added official support for Time Machine much later, but I think it was possible on earlier versions with some extra steps.

▲

throw0101c 2 hours ago | parent [-]

Samba 4.8 from 2018:

* https://www.samba.org/samba/history/samba-4.8.0.html ("vfs_fruit")

* https://wiki.samba.org/index.php/Configure_Samba_to_Work_Bet...

	▲	wtallis an hour ago \| parent [-]
		That's when Samba gained official easy to use support for being used with Time Machine. I'm pretty sure it was possible long before then, IIRC by changing a setting on the Mac to allow selecting unsupported network volumes. I don't recall when I stopped running netatalk on my NAS and switched to pure Samba, but I think it was before 2018.

▲

Melatonic 5 hours ago | parent | prev [-]

SMB1 has major security issues but even those ignored (which a lot of people on private home networks shouldn't be too worried about) it's also slow as hell on MacOS

	▲	riffic 4 hours ago \| parent [-]
		> people on private home networks shouldn't be too worried about philosophically I would beg to differ about any premise assuming we can trust the castle and moat model. Even on home networks.