All of lore.kernel.org
 help / color / mirror / Atom feed
From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: Andreas Hasenack <andreas@canonical.com>
Cc: linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: "Bad SMB2 signature for message" with kernel 5.0.0, works with 4.19.0
Date: Thu, 21 Mar 2019 15:03:18 +1000	[thread overview]
Message-ID: <CAN05THQb3-p=XX=WpCxv1zfP4e3sBLMY54bg+n=wy9HQCOiJiw@mail.gmail.com> (raw)
In-Reply-To: <CANYNYEFJos5tzAyN7kdHKaAVeV_cD8QF8=wAs4XXhu9PXWgE3A@mail.gmail.com>

Hi Andreas.
I have reproduced the issue and sent a patch to the list.
It should show up shortly with the title "cifs: allow guest mounts to
work for smb3.11"

Can you try that patch and verify that it fixes the issue?

Regards
Ronnie Sahlberg

On Thu, Mar 21, 2019 at 4:40 AM Andreas Hasenack <andreas@canonical.com> wrote:
>
> Hi,
>
> I can't mount a share as guest using SMB2 or higher when running the
> 5.0.0 kernel (ubuntu's 5.0.0-7.8 specifically). When I switch to a
> 4.19.x kernel (4.19.0-12-generic), then it works.
>
> This is the mount command and output:
> root@ubuntu:~# mount //localhost/pub /mnt -o guest
> mount error(13): Permission denied
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
>
> The share is a simple one:
> [pub]
> path = /pub
> guest ok = yes
>
> The server logs this:
> [2019/03/20 18:24:46.245816,  0]
> ../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
>   Bad SMB2 signature for message
> [2019/03/20 18:24:46.245860,  0] ../../lib/util/util.c:508(dump_data)
>   [0000] 2D 60 1F CA 49 06 92 B0   69 06 60 82 42 39 21 F8   -`..I... i.`.B9!.
> [2019/03/20 18:24:46.245894,  0] ../../lib/util/util.c:508(dump_data)
>   [0000] 75 F8 77 09 63 D5 4A 7B   9F 91 51 93 6D 12 6F 6F   u.w.c.J{ ..Q.m.oo
>
> Here is a dmesg output with cifs debugging enabled:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821053/+attachment/5247960/+files/dmesg.txt
>
> That output was from a kernel running patch
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch,
> just a quick attempt to see if that fixed it, but it didn't.
>
> mount.cifs is version 6.8
>
> Server is samba 4.10.0.
>
> Is this a known issue?
>
> Thanks!

  parent reply	other threads:[~2019-03-21  5:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 18:39 "Bad SMB2 signature for message" with kernel 5.0.0, works with 4.19.0 Andreas Hasenack
2019-03-20 21:50 ` Paulo Alcantara
2019-03-21  0:14   ` Andreas Hasenack
2019-03-20 22:08 ` Steve French
2019-03-21 14:26   ` Tom Talpey
2019-03-21  1:44 ` Steve French
2019-03-21 12:24   ` Andreas Hasenack
2019-03-21  5:03 ` ronnie sahlberg [this message]
2019-03-21 12:25   ` Andreas Hasenack

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='CAN05THQb3-p=XX=WpCxv1zfP4e3sBLMY54bg+n=wy9HQCOiJiw@mail.gmail.com' \
    --to=ronniesahlberg@gmail.com \
    --cc=andreas@canonical.com \
    --cc=linux-cifs@vger.kernel.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.