Project information - SMBv2+
CerebrosuS at gmx.net
Wed Dec 30 17:54:34 UTC 2020
Am 30.12.20 um 18:30 schrieb Dale Scott:
> ----- Original Message -----
>> From: "Kevin P. Neal" <kpn at neutralgood.org>
>> To: "CerebrosuS" <CerebrosuS at gmx.net>
>> Cc: "freebsd-questions" <freebsd-questions at freebsd.org>
>> Sent: Tuesday, December 29, 2020 7:35:51 PM
>> Subject: Re: Project information - SMBv2+
>> On Mon, Dec 28, 2020 at 10:13:07PM +0100, CerebrosuS wrote:
>>> Hello at all,
>>> the community and developer at FreeBSD seem to know, that SMBv1 for
>>> clients is nearly over and that the included mount_smbfs doesn't support
>>> newer versions. So good, so far...
>>> So I can find multiple information about the situation, but no clear
>>> path on how FreeBSD community and developer will go on to solve this
>>> missing function. (Just got the information on:
> Can someone give a quick big picture? What would this mean for someone e.g.
> wanting to build an enterprise file server? Can FreeBSD currently serve (I see
> latest samba413 is in ports), but not connect as client to other (newer) servers?
The problem is using FreeBSD as an SMB client. SMBv1 is possible through
mount_smbfs. SMBv2+ is possible with gvfs and smbnetfs from fuse. SMBv1
has some bad security issues (thats' why everyone is switching to
SMBv2+) and MS Windows 10 switched to SMBv2+ meaning, SMBv1 is not
supported by default.
The fuse module is known be slow and unstable. I read the "unstable" and
"slow" argument for gvfs too, but have only tested the fuse module.
Third party packages are also problematic when using with /etc/fstab
(there seem to be some workarounds with extension scripts).
So to use freebsd as an SMB client would need to extend the mount_smbfs
module or invest time to speed up smbnetfs/gvfs to make it usable.
For an enterprise file server serving samba is no problem as far as I
know and as long as you don't need to mount SMB sources to serve the data.
Anyone might want to correct me, if my collected information are wrong. :-)
>> Two days with no response... I suggest trying the freebsd-hackers list
>> instead, or the freebsd-arch list if that doesn't work, and my last
>> guess would be freebsd-current. Only try one list at a time.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions