From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: L A Walsh <law-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>,
linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: SMB2: Enforce sec= mount option
Date: Wed, 11 Jan 2017 11:46:36 +0100 [thread overview]
Message-ID: <mpsvatlj2lv.fsf@suse.com> (raw)
In-Reply-To: <58756A3D.6000705-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
L A Walsh <law-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org> writes:
> I'm not sure about the symbols, exactly, but I know in samba I
> ask for smb2 for the protocol and more often than not, only
> get smb1, but I'd rather have it work than fail.
About this specific thing: I believe smbclient negotiate the highest
protocol version it can (according to the min/max protocol version set
in its conf) whereas cifs.ko always uses smb1 by default (which is
probably against the spec).
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-01-11 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 6:46 [PATCH] SMB2: Enforce sec= mount option Sachin Prabhu
[not found] ` <1481179577-15995-1-git-send-email-sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-08 8:06 ` Scott Lovenberg
[not found] ` <CAFB9KM0oPPm4bYyKd75Yjy-2kCZ=0UTpwn=ONCRo0g5waNa6AA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-08 9:03 ` Sachin Prabhu
[not found] ` <1481187800.4195.19.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-08 9:14 ` Scott Lovenberg
2017-01-11 11:45 ` Germano Percossi
[not found] ` <c0748fb1-4161-ea0f-3f6d-b0705bb83a9d-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2017-01-11 12:17 ` Sachin Prabhu
[not found] ` <1484137071.29387.9.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-11 17:48 ` Scott Lovenberg
[not found] ` <CAH2r5mvU4_O_epw8tTPOHV3UVRyi9eNmE85cFPGVDGR8twQiZg@mail.gmail.com>
[not found] ` <CAH2r5mvU4_O_epw8tTPOHV3UVRyi9eNmE85cFPGVDGR8twQiZg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-11 17:59 ` Fwd: " Steve French
2017-01-10 23:11 ` L A Walsh
[not found] ` <58756A3D.6000705-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
2017-01-11 10:46 ` Aurélien Aptel [this message]
2017-01-11 21:02 ` Scott Lovenberg
[not found] ` <CAFB9KM3S+p3sU26LKGwqaZ_3g4gkPPzEFzohwAFOa-PZPqZTAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-12 4:23 ` Steve French
2017-01-12 10:33 ` L A Walsh
2017-01-16 5:49 ` Sachin Prabhu
2017-01-10 23:30 ` L A Walsh
[not found] ` <CAH2r5msW1Z1j3J+c3RF7NAH9ChKxy2GajKNp7AUxF4sfeZPXUA@mail.gmail.com>
[not found] ` <CAH2r5msW1Z1j3J+c3RF7NAH9ChKxy2GajKNp7AUxF4sfeZPXUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-10 20:23 ` Fwd: [PATCH] " Steve French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mpsvatlj2lv.fsf@suse.com \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=law-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.