From owner-freebsd-fs@freebsd.org Wed Sep 27 13:11:33 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 8E9C1E037C5; Wed, 27 Sep 2017 13:11:33 +0000 (UTC) (envelope-from mlobo@digiart.art.br) Received: from burlywood.maple.relay.mailchannels.net (burlywood.maple.relay.mailchannels.net [23.83.214.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3764671F6E; Wed, 27 Sep 2017 13:11:31 +0000 (UTC) (envelope-from mlobo@digiart.art.br) X-Sender-Id: hostmach|x-authuser|mlobo@digiart.art.br Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 62050127EA9; Wed, 27 Sep 2017 13:04:49 +0000 (UTC) Received: from logan.hmnoc.net (unknown [100.96.147.85]) (Authenticated sender: hostmach) by relay.mailchannels.net (Postfix) with ESMTPA id C130E127D15; Wed, 27 Sep 2017 13:04:48 +0000 (UTC) X-Sender-Id: hostmach|x-authuser|mlobo@digiart.art.br Received: from logan.hmnoc.net (logan.hmnoc.net [100.96.147.1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Wed, 27 Sep 2017 13:04:49 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: hostmach|x-authuser|mlobo@digiart.art.br X-MailChannels-Auth-Id: hostmach X-Army-Obese: 4579a14b32d0c674_1506517489231_3162370249 X-MC-Loop-Signature: 1506517489231:1720677985 X-MC-Ingress-Time: 1506517489230 Received: from [187.113.116.71] (port=65170 helo=Papi.lobos) by logan.hmnoc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dxC18-002CZP-My; Wed, 27 Sep 2017 10:04:47 -0300 Date: Wed, 27 Sep 2017 10:06:35 -0300 From: Mario Lobo To: freebsd-fs@freebsd.org Cc: FreeBSD questions Subject: mount_smbfs question (re-post) Message-ID: <20170927100635.7b56f8fd@Papi.lobos> Organization: DigiArt X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AuthUser: mlobo@digiart.art.br 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: Wed, 27 Sep 2017 13:11:33 -0000 Please forgive my repost. I've searching for an answer to this for quite a while and the only 2 most recent links I found on the subject were: https://forums.freebsd.org/threads/61374/ https://forums.freebsd.org/threads/61422/ and they both say basically this: "mount_smbfs only supports SMBv1 which may be disabled on your sharing machines due to the WannaCry outbreak. There are no definite plans to add support for SMBv2 or SMBv3 to mount_smbfs." and "I cannot turn on SMBv1 for the handful of systems because the OS hasn't updated to work with something that has been out for over 10 years. While NFS might be an easier route in the "now", it is the principle of the matter. Who knows what other common features in the future will just get left behind because they aren't updated for integration. I do get that BSD is community ran and funded. SMBv1 has been around since 1990 and SMBv2 came out 11 years ago in 2006. Linux has moved ahead and kept up with their security. It makes me sad that BSD hasn't made any movement to keep up with SMB security versions" Since my environment is tottaly surrounded with shares that no longer accept SMBv1 (Windows, Linux AND FreeBSD servers), so basically in the end, what I'm really looking for is a confirmation that I'll just have to dump all Freebsd samba clients because the OS can't deal with SMBv2 or above. Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things."