From owner-freebsd-current@freebsd.org  Tue Mar  8 12:53:58 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 8F907AC742A
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  8 Mar 2016 12:53:58 +0000 (UTC)
 (envelope-from ohartman@zedat.fu-berlin.de)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de
 [130.133.4.66])
 (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 204227B5;
 Tue,  8 Mar 2016 12:53:58 +0000 (UTC)
 (envelope-from ohartman@zedat.fu-berlin.de)
Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69])
 by outpost.zedat.fu-berlin.de (Exim 4.85)
 with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256)
 (envelope-from <ohartman@zedat.fu-berlin.de>)
 id <1adH94-002eA7-GL>; Tue, 08 Mar 2016 13:53:50 +0100
Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249]
 helo=freyja.zeit4.iv.bundesimmobilien.de)
 by inpost2.zedat.fu-berlin.de (Exim 4.85)
 with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128)
 (envelope-from <ohartman@zedat.fu-berlin.de>)
 id <1adH94-000YGP-7c>; Tue, 08 Mar 2016 13:53:50 +0100
Date: Tue, 8 Mar 2016 13:53:44 +0100
From: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To: Edward Tomasz =?ISO-8859-1?Q?Napiera=3Fa?= <trasz@FreeBSD.org>
Cc: freebsd-current <freebsd-current@freebsd.org>
Subject: Re: mount_smbfs(8): support for SMBv3.02?
Message-ID: <20160308135344.75e06913@freyja.zeit4.iv.bundesimmobilien.de>
In-Reply-To: <20160308095525.GA1872@brick.home>
References: <20160303104721.097ae352@freyja.zeit4.iv.bundesimmobilien.de>
 <20160308095525.GA1872@brick.home>
Organization: FU Berlin
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: 87.138.105.249
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2016 12:53:58 -0000

On Tue, 8 Mar 2016 10:55:25 +0100
Edward Tomasz Napiera=C5=82a <trasz@FreeBSD.org> wrote:

> On 0303T1047, O. Hartmann wrote:
> > Does FreeBSD's mount_smbfs(8) support for Microsoft's SMBv3 protocol
> > introduced with Windows 8 and Windows Server 2012/R2? =20
>=20
> No, it only supports the obsolete SMB1 (aka CIFS) protocol.  Since SMB2
> is a completely different protocol, supporting it properly pretty much
> requires implementing it from scratch.  SMB3 is one of the SMB2 revisions
> and thus is backward compatible with SMB2.
>=20
[...]

Thank you very much for this clearification. This explains much strange
behaviour I faced.

Do you see any chance that this gets fixed in a forseable time? Linux seems=
 to
support SMBv3 by now. Or is a support considered obsolete and handled
via /net/samba43?

For a security appliance, I try to avoid as much packages as possible, so
therefore my concerns regarding mount_smbfs.

Thanks you very much,

O. Hartmann