SMBv1 Deprecation

[Stefan Esser]

Am 23.06.17 um 15:42 schrieb Matt B:
> I have used the netsmb fuse module. It doesn't like being mounted via
> fstab. I had to modify the source code to get it to even try to mount
> from fstab, and even then it was clunky. I think the best way forward is
> to get mount_smbfs working with SMBv2 or higher. I'd love to get this
> working properly. I just don't know where to start here. Should I focus
> on getting smbfs updated? Is it even necessary to do that? Is the
> problem with just how mount_smbfs communicates with the share? Any ideas
> would be great.

The smbfs code in the kernel is responsible for all communication with
the SMB server. You need to make that support SMB2 (or SMB3) client
operations.

A specification of the SMB2/3 protocol can be downloaded from Microsoft:

http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/%5BMS-SMB2%5D.pdf

Implementing the client is a lot simpler compared to a server,
since you can rely on the server working according to the spec and
only have to implement the subset of functionality you need to
provide open/close/read/write/delete for the protocol version that
appears most appropriate (and you can ignore all optional features
that are not strictly necessary to get access to the server).

But it'd be quite and undertaking, I assume ...

Regards, STefan