SMB1/SMB2.0 can be disabled fairly easily in the Linux client build, but there are occasional requests for it due to SMB1/CIFS still being used to access some old devices. Also some of the SMB1 code was moved to SMB1 specific files to make that clearer, and to make the module smaller when SMB1/SMB2.0 is not enabled. Even when SMB1/SMB2.0 is configured in the build, in the future it may be useful to not load the SMB1 specific files (put them in a helper module that contains all of the SMB1 specific code, rather in the main filesystem module) unless the user specifies "vers=1.0" on mount. On Sun, Nov 10, 2024 at 7:13 PM Jeremy Allison <jra@xxxxxxxxx> wrote: > > On Mon, Nov 11, 2024 at 09:02:03AM +1000, ronnie sahlberg wrote: > >All of SMB1 should be removed. Not just disabled but deleted. > > > >What are the plans in samba? Any timeline to literally delete the smb1 code? > > It can already be compiled out of any build, > so it's an option for any distro or user of > Samba. > > I'm not sure deleting the code is needed at > this point, as it still has legacy uses > (there are still commercial uses of OS/2 > out there for example). -- Thanks, Steve
