Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: steve <steve-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
To: Jurjen Bokma <j.bokma-39IHFo8E5E0@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Kerberized mount.cifs with SMB>1?
Date: Mon, 20 Oct 2014 18:24:23 +0200	[thread overview]
Message-ID: <54453737.7040403@steve-ss.com> (raw)
In-Reply-To: <54442399.5030100-39IHFo8E5E0@public.gmane.org>

On 19/10/14 22:48, Jurjen Bokma wrote:
> On 10/19/2014 10:42 PM, steve wrote:
>> On 19/10/14 22:30, Jurjen Bokma wrote:
>>
>>> So I would very much like to use SMB3 to get to the Windows file
>>> servers. Kerberized SMB1 worked like a charm. Speed/bandwidth is not
>>> really the issue here.
>>>
>> Yeah, of course. Never knew there was any security involved. Worrying.
> Did you ever have SMB3 working Kerberized? If I know it's supposed to
> work, I'll give up less easily.
>
Hi
We have everything default. We'd no idea that smb3 existed until this 
thread. Anyway, it doesn't work here either:
CIFS VFS: cifs_mount failed w/return code = -128
I think the Kerberos has worked because that codes means that the ticket 
has expired, except it hasn't because removing vers=3.0 mounts fine.
But we don't know if our Samba4 file servers are capable of it anyway. I 
think we'd have to change something in smb.conf.

Maybe the devs will look if you bugzilla it?
Good luck,
Steve

  parent reply	other threads:[~2014-10-20 16:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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)
  -- strict thread matches above, loose matches on Subject: below --
2015-07-24 10:09 Noel Power

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=54453737.7040403@steve-ss.com \
    --to=steve-dz4o0aztnmbwk0htik3j/w@public.gmane.org \
    --cc=j.bokma-39IHFo8E5E0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox