From owner-freebsd-fs@freebsd.org Fri Jun 23 16:30:29 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76FB5DA79C5 for ; Fri, 23 Jun 2017 16:30:29 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout11.t-online.de (mailout11.t-online.de [194.25.134.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 389BC6657E for ; Fri, 23 Jun 2017 16:30:28 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd40.aul.t-online.de (fwd40.aul.t-online.de [172.20.26.139]) by mailout11.t-online.de (Postfix) with SMTP id 92D1F426480B; Fri, 23 Jun 2017 18:30:25 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (V+6lcrZSohttEn4-z8ek25wNYgPBNa40-6INFtcUJNAIiFwNpbQwoH67o6SsB7WQlB@[84.154.108.252]) by fwd40.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dORTT-0h3Fk80; Fri, 23 Jun 2017 18:30:23 +0200 Subject: Re: SMBv1 Deprecation To: Matt B Cc: Stefan Esser , "freebsd-fs@freebsd.org" References: <9b556cbe-f9f3-ab15-6fcd-71397d18c126@freebsd.org> <20170623104654.07e5a3e0@ernst.home> <45b0864b-680c-8fe0-f5a5-353b6373d069@freebsd.org> From: Stefan Esser Message-ID: <3e73e276-0e8d-ec88-5d25-58fdff2d27a6@freebsd.org> Date: Fri, 23 Jun 2017 18:30:23 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ID: V+6lcrZSohttEn4-z8ek25wNYgPBNa40-6INFtcUJNAIiFwNpbQwoH67o6SsB7WQlB X-TOI-MSGID: 06f944e4-7b09-45a3-a9c1-eba200c86d5d X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 16:30:29 -0000 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