From: Noel Power <nopower-IBi9RG/b67k@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: Kerberized mount.cifs with SMB>1?
Date: Fri, 24 Jul 2015 11:09:11 +0100 [thread overview]
Message-ID: <55B20EC7.5040502@suse.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Hi Steve, *
I came across this thread
http://thread.gmane.org/gmane.linux.kernel.cifs/10081/focus=10305 when
investigating why mount.cifs wasn't working with smb2. I have tried to
follow the information there and have created a patch. I have tested
this successfully against SMB2.0, SMB2.1, SMB3.0, SMB3.02.
Regarding the patch I followed as much as I could sess_auth_kerberos
method in cifs.c[1]. Some things I didn't quite see how to handle as
they don't seem relevant in SMB2 e.g. the unicode_oslm_strings,
unicode_domain_string, ascii_ssetup_strings handling, also I only just
noticed I missed the "bad security blob length" check (but not sure if
it is needed for smb1+) Anyway be interested in a review of the patch :-)
thanks,
Noel
[1] actually I followed CIFS_SessSetup of an older cifs version but then
when rebasing glanced at the new 'sess_auth_kerberos'
[-- Attachment #2: 0001-kerberos-mount-for-SMB2-SMB3.patch --]
[-- Type: application/mbox, Size: 8187 bytes --]
next reply other threads:[~2015-07-24 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 10:09 Noel Power [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-20 14:08 Kerberized mount.cifs with SMB>1? Jurjen Bokma
[not found] ` <53F4ABCD.5040909-39IHFo8E5E0@public.gmane.org>
2014-08-20 14:43 ` steve
[not found] ` <1408545832.2071.6.camel-HkULYb+WTT7YCGPCin2YbQ@public.gmane.org>
2014-08-20 17:16 ` Jurjen Bokma
[not found] ` <53F4D7FC.8020405-39IHFo8E5E0@public.gmane.org>
2014-10-19 19:58 ` Jurjen Bokma
[not found] ` <544417CA.3000609-39IHFo8E5E0@public.gmane.org>
2014-10-19 20:25 ` steve
[not found] ` <54441E2A.6020809-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
2014-10-19 20:30 ` Jurjen Bokma
[not found] ` <54441F79.7040804-39IHFo8E5E0@public.gmane.org>
2014-10-19 20:42 ` steve
[not found] ` <54442233.4090801-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
2014-10-19 20:48 ` Jurjen Bokma
[not found] ` <54442399.5030100-39IHFo8E5E0@public.gmane.org>
2014-10-20 16:24 ` steve
[not found] ` <54453737.7040403-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
2014-10-20 16:37 ` Jurjen Bokma
[not found] ` <54453A48.1050208-39IHFo8E5E0@public.gmane.org>
2014-10-20 17:09 ` Steve French
[not found] ` <CAH2r5msA2D8upKSYVUEC1ygULe9oGa2x0XR5tGeF59bSmjKa3g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-20 17:19 ` Jurjen Bokma
2014-08-20 14:44 ` McCall, Andy (IT.PFMS)
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=55B20EC7.5040502@suse.com \
--to=nopower-ibi9rg/b67k@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=noel.power-IBi9RG/b67k@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@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.