Re: Mounting share on NetApp using SMB 3.1.1 and encryption

["Aurélien Aptel" <aaptel@suse.com>]

Till Dörges <doerges@pre-sense.de> writes:
> Apart from the security requirements the server uses DFS and nested name spaces.

The nested namespace might be problematic. DFS is tricky.

> So before digging any further, I'm wondering whether this should generally work with 
> options "seal,vers=3.1.1", what to make of the ciphers requirement.

I think by default the client will only show support for up to 3.0
unless you ask it to.
So apart from the version, encryption and ciphers should be
auto-negotiated during the connection establishement: the client sends
its feature support, the server replies with its requirement. If the
requirements cannot be met the client will fail.

I believe you should only have to put vers=3.1.1. By putting seal you
are asking the client to make encryption a requirement instead of
letting the server decide.

If you are having issues connecting please refer to the wiki on
reporting cifs.ko bugs for instructions on how to debug things further:

https://wiki.samba.org/index.php/Bug_Reporting#cifs.ko

Cheers,
-- 
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)