On Mon, 13 Aug 2018 09:30:14 -0500, Steve French wrote: > We could add versions if that helped make it less confusing for users, > but the main motivation here is how to deal with the confusion of > users being told 'do not use cifs' (the dialect, due to 20 year old > security) and getting confused when we tell them to use commands > with 'cifs' in them. Isn't that confusion already encountered once the user needs to run "mount -t cifs"? > Using 'SMB' on the other hand may be ok, except > SMB (SMB1) was invented in 1984 and is not really very > closely related to SMB3 and later, which share common characteristics > and are highly secure (SMB3, SMB3.02 SMB3.1.1), and some admins > may think of SMB = SMB1 = 'even more insecure, don't ever, ever use > that on a public network' > while SMB3 is highly secure. My preference would be to keep the original pseudo-xattr names until the cifs.ko kernel module is (if ever) renamed. There are bound to be many many other places where "cifs" is used, and renaming bit-by-bit doesn't make much sense IMO. Cheers, David
